Triple
T27882613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Collis P. Huntington |
E705131
|
entity |
| Predicate | namedTrainOf |
P76033
|
FINISHED |
| Object | C&O Railway |
—
|
NE NERFINISHED |
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: C&O Railway | Statement: [The Collis P. Huntington, namedTrainOf, C&O Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedTrainOf Context triple: [The Collis P. Huntington, namedTrainOf, C&O Railway]
-
A.
servedByNamedTrain
Indicates that a service, route, or journey is operated specifically by a train with a particular designated name.
-
B.
notableTrain
Indicates that there is a train or rail service associated with the subject that is considered notable or significant in some way.
-
C.
usesTrainNumber
Indicates that one entity operates, identifies, or references another entity by a specific train number.
-
D.
trains
Indicates that one entity teaches, instructs, or coaches another entity to develop skills, knowledge, or abilities.
-
E.
namedTrainAssociation
chosen
Indicates an association between a specific train and a designated name or service label assigned to that train.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 6:31 p.m.