Triple
T27882606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Collis P. Huntington |
E705131
|
entity |
| Predicate | namedServiceOf |
P171439
|
FINISHED |
| Object | Chesapeake and Ohio 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: Chesapeake and Ohio Railway | Statement: [The Collis P. Huntington, namedServiceOf, Chesapeake and Ohio Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedServiceOf Context triple: [The Collis P. Huntington, namedServiceOf, Chesapeake and Ohio Railway]
-
A.
namedTo
Indicates that one entity has been given or assigned a specific name referring to another entity.
-
B.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
C.
namedForOrganization
Indicates that one entity bears a name that is derived from or given in honor of a particular organization.
-
D.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
E.
namedAs
Indicates that one entity is given, known by, or referred to using the name of another entity.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 27, 2026, 6:31 p.m.