Triple
T2417027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York, New Haven and Hartford Railroad |
E52327
|
entity |
| Predicate | operatedEquipmentType |
P15250
|
FINISHED |
| Object | steam locomotives |
—
|
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: steam locomotives | Statement: [New York, New Haven and Hartford Railroad, operatedEquipmentType, steam locomotives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedEquipmentType Context triple: [New York, New Haven and Hartford Railroad, operatedEquipmentType, steam locomotives]
-
A.
typeOfEquipmentManaged
chosen
Indicates the specific kind or category of equipment that an entity is responsible for managing.
-
B.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
C.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
D.
operatedWith
Indicates that an entity performed an action, function, or process using a specified tool, method, or instrument.
-
E.
typeOfCanalOperated
Indicates that one entity operates or manages a canal of the specified type.
- 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_69ab495622948190bc6bc6e4cddaf645 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc94eafd481909eeff689e5bf5960 |
completed | March 7, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69abc5a6cbd0819086c0716e266b7ebb |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:42 p.m.