Triple
T18747671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian broad gauge |
E458445
|
entity |
| Predicate | trackCenterDistanceTypical |
P103291
|
FINISHED |
| Object | about 4.265 m (varies by standard) |
—
|
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: about 4.265 m (varies by standard) | Statement: [Indian broad gauge, trackCenterDistanceTypical, about 4.265 m (varies by standard)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackCenterDistanceTypical Context triple: [Indian broad gauge, trackCenterDistanceTypical, about 4.265 m (varies by standard)]
-
A.
typicalLinkDistance
Indicates the usual or characteristic distance that typically separates two linked or related entities.
-
B.
distanceFromCentre
chosen
Indicates the measured or specified distance of an entity from a defined central point.
-
C.
haveTypicalApproachDistance
Indicates that there is a characteristic or standard distance typically maintained when approaching something.
-
D.
typicalTrackLengthRange
Indicates the usual minimum and maximum lengths that a track associated with something tends to fall between.
-
E.
typicalLength
Indicates the usual or characteristic length associated with an entity or phenomenon.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579e9903c81908180c46012bd0948 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.