Triple
T20088748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nickel Plate Road 2-8-4 Berkshires |
E496208
|
entity |
| Predicate | operatedOnGauge |
P138675
|
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: [Nickel Plate Road 2-8-4 Berkshires, operatedOnGauge, standard gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedOnGauge Context triple: [Nickel Plate Road 2-8-4 Berkshires, operatedOnGauge, standard gauge]
-
A.
operatedOn
Indicates that one entity has performed a surgical or procedural operation on another entity.
-
B.
operatedOnLevel
Indicates that an action or process was performed at, or with respect to, a specific level or layer within a system or structure.
-
C.
operatedWith
Indicates that an entity performed an action, function, or process using a specified tool, method, or instrument.
-
D.
operatedTo
Indicates that one entity has performed a surgical or medical operation on another entity.
-
E.
operatedFor
Indicates that one entity performed operations or provided services on behalf of, or in support of, another entity for a certain period or purpose.
- F. None of above. chosen
Provenance (4 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655d65a88190a510132f36341b6c |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:17 p.m.