Triple
T18747654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian broad gauge |
E458445
|
entity |
| Predicate | trackStability |
P93629
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Indian broad gauge, trackStability, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackStability Context triple: [Indian broad gauge, trackStability, high]
-
A.
trainingStability
Indicates the degree to which a training process proceeds consistently without large fluctuations, divergence, or instability in its behavior or outcomes.
-
B.
stabilityCharacteristic
chosen
Indicates that one entity specifies a property or feature related to the stability or steadiness of another entity or system.
-
C.
trackGauge
Indicates the distance between the inner faces of the rails in a railway track system.
-
D.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
-
E.
trackingAvailable
Indicates that tracking information or functionality is available for the associated item, process, or interaction.
- 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.