Triple
T36617593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Jahili Fort |
E903645
|
entity |
| Predicate | locatedInOasisCity |
P204966
|
FINISHED |
| Object | Al Ain Oasis region |
E1040873
|
NE 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: Al Ain Oasis region | Statement: [Al Jahili Fort, locatedInOasisCity, Al Ain Oasis region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInOasisCity Context triple: [Al Jahili Fort, locatedInOasisCity, Al Ain Oasis region]
-
A.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
isInCity
Indicates that one entity is located within the geographical boundaries of a specified city.
-
C.
housedInCity
Indicates that one entity (such as a building, organization, or facility) is located within and contained by a particular city.
-
D.
areLocatedAt
Indicates that one or more entities occupy or exist at a specific location or place.
-
E.
deployedInCity
Indicates that an entity has been placed into active use or operation within a particular city.
- F. None of above. chosen
Provenance (5 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a095da0fc81909f74bbe3a45e1702 |
completed | June 23, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.