Triple
T10606040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMRDA Metro |
E275878
|
entity |
| Predicate | systemLengthUnit |
P6008
|
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: [MMRDA Metro, systemLengthUnit, kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemLengthUnit Context triple: [MMRDA Metro, systemLengthUnit, kilometres]
-
A.
unitSystem
Indicates the system of measurement units (such as metric or imperial) that is used to quantify associated values or attributes.
-
B.
dimensionOfLength
Indicates that something represents or specifies a measurement along a single spatial extent (a length dimension).
-
C.
USUnit
Indicates that the associated quantity or measurement is expressed using United States customary units (e.g., feet, pounds, gallons) rather than other unit systems.
-
D.
typeOfUnit
chosen
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
-
E.
isOfficialSystemOfUnitsFor
Indicates that one system of units is formally recognized or designated as the standard measurement system for a particular domain, region, or context.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4a5df88190b993196ca7849a88 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
Created at: April 8, 2026, 7:32 p.m.