Triple
T18542354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ain Dubai |
E453130
|
entity |
| Predicate | rotationDuration |
P101443
|
FINISHED |
| Object | approximately 38 minutes |
—
|
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: approximately 38 minutes | Statement: [Ain Dubai, rotationDuration, approximately 38 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationDuration Context triple: [Ain Dubai, rotationDuration, approximately 38 minutes]
-
A.
swingSpanRotationTime
chosen
Indicates the amount of time required for a swing span (such as a rotating bridge section) to complete its rotational movement from one position to another.
-
B.
rotationEffect
Indicates that one entity is rotated around a specified point or axis by a given angle, affecting its orientation relative to other entities.
-
C.
rotationType
Indicates the specific kind or mode of rotational movement or orientation applied in a given context.
-
D.
rotationProcess
Indicates a process in which something is turned or rotated around an axis or point over time.
-
E.
rotationPractice
Indicates that an entity engages in or is involved with practicing rotational movements or rotation-related skills.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534b80fc081908488417787d1b166 |
completed | April 19, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:38 a.m.