Triple
T19414188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Fahidi Metro Station |
E485664
|
entity |
| Predicate | hasSystemLengthUnit |
P135787
|
FINISHED |
| Object | kilometres |
—
|
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: kilometres | Statement: [Al Fahidi Metro Station, hasSystemLengthUnit, kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSystemLengthUnit Context triple: [Al Fahidi Metro Station, hasSystemLengthUnit, kilometres]
-
A.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
B.
dimensionOfLength
Indicates that something represents or specifies a measurement along a single spatial extent (a length dimension).
-
C.
isOfficialSystemOfUnitsFor
Indicates that one system of units is formally recognized or designated as the standard measurement system for a particular domain, region, or context.
-
D.
hasBaselineLength
Indicates that one entity has a specified baseline length measurement in relation to another entity or reference.
-
E.
properLengthMeasuredIn
Indicates that the proper (intrinsic or rest-frame) length of an entity is expressed using a specified unit of measurement.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af834fc81908cb176076de10c1c |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.