Triple
T36355225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dadan |
E895322
|
entity |
| Predicate | laterNeighbor |
P202649
|
FINISHED |
| Object | Nabataean kingdom |
—
|
NE NERFINISHED |
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: Nabataean kingdom | Statement: [Dadan, laterNeighbor, Nabataean kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterNeighbor Context triple: [Dadan, laterNeighbor, Nabataean kingdom]
-
A.
innerNeighbor
Indicates that one entity is directly adjacent to another entity on the inside or interior side of a boundary or structure.
-
B.
outerNeighbor
Indicates that one entity is adjacent to another from the outside, typically sharing a boundary but not being contained within it.
-
C.
neighboringTo
Indicates that one entity is located directly adjacent or very close to another entity, sharing a common boundary or immediate vicinity.
-
D.
formerNeighbor
Indicates that one entity used to live near or next to the other entity but no longer does.
-
E.
laterLocation
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
- F. None of above. chosen
Provenance (4 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00a602b6b48190a9dea8ae22d2fa05 |
completed | May 10, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_6a00a559bf3881909a7b50776d8f47bb |
completed | May 10, 2026, 3:33 p.m. |
| PDg | Predicate description generation | batch_6a00a601ff988190b3eb7a9abc92a557 |
completed | May 10, 2026, 3:36 p.m. |
Created at: May 3, 2026, 4:09 p.m.