Triple
T4707002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Shindagha Tunnel |
E104411
|
entity |
| Predicate | connectsSideOfCreek |
P33399
|
FINISHED |
| Object | Bur Dubai side |
—
|
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: Bur Dubai side | Statement: [Al Shindagha Tunnel, connectsSideOfCreek, Bur Dubai side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsSideOfCreek Context triple: [Al Shindagha Tunnel, connectsSideOfCreek, Bur Dubai side]
-
A.
connectsViaCanal
Indicates that one entity is linked or joined to another by means of a canal.
-
B.
locatedAcrossRiverFrom
Indicates that one entity is situated on the opposite side of a river relative to another entity.
-
C.
riverBankOnOneSide
Indicates that a river flows adjacent to and borders only one side of a specified bank or land area.
-
D.
reachedRiver
Indicates that an entity has arrived at or come into contact with a river as a result of movement or travel.
-
E.
riverCrossingConnection
chosen
Indicates a connection between two locations that are linked by a route or structure specifically used to cross a river.
- 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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.