Triple
T32400772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Hamburg, New York |
E827942
|
entity |
| Predicate | railLineFormerOwner |
P96078
|
FINISHED |
| Object | New York Central Railroad |
—
|
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: New York Central Railroad | Statement: [New Hamburg, New York, railLineFormerOwner, New York Central Railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railLineFormerOwner Context triple: [New Hamburg, New York, railLineFormerOwner, New York Central Railroad]
-
A.
followsFormerRailroad
Indicates that something is aligned with or traces the route of a former railroad line.
-
B.
railwayOwner
chosen
Indicates that one entity owns, controls, or holds proprietary rights over a railway or railway system used by another entity.
-
C.
formerRailwayLine
Indicates that a railway line previously existed in the past but is no longer in operation or has been decommissioned.
-
D.
railLineBuiltBy
Indicates that a particular rail line was constructed or developed by a specified agent, such as a company, organization, or authority.
-
E.
laterRailwayCompany
Indicates that one railway company is the successor or later incarnation of another railway company.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c21a287c8190a5b89658ed837f5d |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:52 a.m.