Triple
T6462540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Thumb (locomotive) |
E142154
|
entity |
| Predicate | trackGaugeUsed |
P391
|
FINISHED |
| Object | Baltimore and Ohio Railroad main line 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: Baltimore and Ohio Railroad main line gauge | Statement: [Tom Thumb (locomotive), trackGaugeUsed, Baltimore and Ohio Railroad main line gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackGaugeUsed Context triple: [Tom Thumb (locomotive), trackGaugeUsed, Baltimore and Ohio Railroad main line gauge]
-
A.
trackGauge
chosen
Indicates the distance between the inner faces of the rails in a railway track system.
-
B.
trackUsage
Indicates that one entity monitors and records how another entity or resource is being used over time.
-
C.
trackRecordUsedFor
Indicates that a track record is utilized as a basis or input for some subsequent decision, evaluation, or process.
-
D.
mainTrackDistance
Indicates the distance measured along the primary or main track between two referenced points or entities.
-
E.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
- 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_69c008d2f91c8190a8178767a35e08fc |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c069f7e5908190ae4d8da2b14d274f |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:49 p.m.