Triple
T3698083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amorites |
E78505
|
entity |
| Predicate | originDirection |
P15748
|
FINISHED |
| Object | west of Mesopotamia |
—
|
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: west of Mesopotamia | Statement: [Amorites, originDirection, west of Mesopotamia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originDirection Context triple: [Amorites, originDirection, west of Mesopotamia]
-
A.
offsetDirection
chosen
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
B.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
C.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
D.
orientation
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
-
E.
orientationInducedBy
Indicates that the orientation of one entity is determined or caused by the orientation or configuration of another entity.
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc512ba188190a15bcacafac3f476 |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.