Triple
T24847070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic and Great Western Railroad |
E621778
|
entity |
| Predicate | trackGaugeConvertedTo |
P120311
|
FINISHED |
| Object | standard gauge |
—
|
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: standard gauge | Statement: [Atlantic and Great Western Railroad, trackGaugeConvertedTo, standard gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackGaugeConvertedTo Context triple: [Atlantic and Great Western Railroad, trackGaugeConvertedTo, standard gauge]
-
A.
trackGauge
Indicates the distance between the inner faces of the rails in a railway track system.
-
B.
formerTrackGauge
Indicates that an entity previously had a specified track gauge, which has since been changed or is no longer in use.
-
C.
trackGaugeOptions
Indicates the available or applicable gauge (measurement) configurations that can be used for a given track.
-
D.
convertedToStandardGauge
chosen
Indicates that something previously using a different gauge has been changed or adapted to conform to a standard gauge specification.
-
E.
trackContribution
Indicates that one entity records, monitors, or keeps a history of another entity’s contributions or inputs.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:20 a.m.