Triple
T12932681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celaenae |
E309421
|
entity |
| Predicate | strategicLocationReason |
P30171
|
FINISHED |
| Object | control of routes between the Anatolian plateau and western Asia Minor |
—
|
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: control of routes between the Anatolian plateau and western Asia Minor | Statement: [Celaenae, strategicLocationReason, control of routes between the Anatolian plateau and western Asia Minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicLocationReason Context triple: [Celaenae, strategicLocationReason, control of routes between the Anatolian plateau and western Asia Minor]
-
A.
strategicLocation
Indicates that an entity is positioned in a place of particular tactical or strategic importance relative to goals, resources, or other entities.
-
B.
strategicReason
Indicates that one entity serves as a reason, justification, or motivation for another entity’s strategic decision, plan, or action.
-
C.
reasonForLocation
chosen
Indicates the cause, purpose, or justification for why an entity is at a particular location.
-
D.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
E.
reasonForDeployment
Indicates the underlying cause, purpose, or justification for which an entity is deployed or put into operation.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.