Triple
T14601848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anshan (Persia) |
E342722
|
entity |
| Predicate | approximateLocationRelativeTo |
P22067
|
FINISHED |
| Object | northeast of modern Shiraz |
—
|
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: northeast of modern Shiraz | Statement: [Anshan (Persia), approximateLocationRelativeTo, northeast of modern Shiraz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateLocationRelativeTo Context triple: [Anshan (Persia), approximateLocationRelativeTo, northeast of modern Shiraz]
-
A.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
-
B.
hasApproximateCoordinates
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
-
C.
hasApproximateLocation
chosen
Indicates that an entity is associated with a location that is known only imprecisely or within a general area rather than an exact position.
-
D.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
-
E.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb43a1bb48190bf520cb961f15b5e |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.