Triple
T27750640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Othello (board game) |
E702103
|
entity |
| Predicate | strategyDepth |
P120042
|
FINISHED |
| Object | high |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: high | Statement: [Othello (board game), strategyDepth, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategyDepth Context triple: [Othello (board game), strategyDepth, high]
-
A.
searchDepth
chosen
Indicates the extent or level to which a search process explores through layers, steps, or hierarchy within a structure or space.
-
B.
testDepth
Indicates that an entity is evaluated or measured based on how deep or thorough it is, often in terms of levels, layers, or extent below a surface or baseline.
-
C.
depth
Indicates the vertical distance from a reference surface or top point down to a lower point or bottom within a medium or space.
-
D.
hierarchyDepth
Indicates the level or distance of an entity from the top (root) within a hierarchical structure.
-
E.
maximumDepth
Indicates the greatest extent or deepest level reached by something within a given context or structure.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 4:20 p.m.