Triple
T24104495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu Dhabi–Dubai border |
E597183
|
entity |
| Predicate | separatesMajorCities |
P155077
|
FINISHED |
| Object | Abu Dhabi |
—
|
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: Abu Dhabi | Statement: [Abu Dhabi–Dubai border, separatesMajorCities, Abu Dhabi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatesMajorCities Context triple: [Abu Dhabi–Dubai border, separatesMajorCities, Abu Dhabi]
-
A.
mainCities
Indicates that the related entities are the primary or most important cities associated with a given region, country, or area.
-
B.
otherMajorCity
Indicates that one city is another major city associated with or comparable in importance or status to the first city.
-
C.
connectsMajorCity
Indicates that one entity serves as a link or route providing direct connection to a major city.
-
D.
majorUrbanCenterIn
Indicates that a city or metropolitan area functions as a primary or significant urban center within the specified region or administrative unit.
-
E.
connectsLargestCitiesOf
Indicates a relationship where something (typically a route, network, or infrastructure) links together the largest cities within a specified region or set.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de1399108190986f604468cd5858 |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 11:01 p.m.