Triple
T32400771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Hamburg, New York |
E827942
|
entity |
| Predicate | railLineOwner |
P128129
|
FINISHED |
| Object | Metro-North 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: Metro-North Railroad | Statement: [New Hamburg, New York, railLineOwner, Metro-North Railroad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railLineOwner Context triple: [New Hamburg, New York, railLineOwner, Metro-North Railroad]
-
A.
railwayOwner
Indicates that one entity owns, controls, or holds proprietary rights over a railway or railway system used by another entity.
-
B.
ownsRailwayLine
chosen
Indicates that one entity has legal ownership or control over a railway line used for train operations.
-
C.
railLineBuiltBy
Indicates that a particular rail line was constructed or developed by a specified agent, such as a company, organization, or authority.
-
D.
railFranchise
Indicates a contractual relationship in which a company is granted the right to operate rail services or manage rail infrastructure within a specified area or route.
-
E.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
- 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_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:52 a.m.