Triple
T30709926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MNR Noroton Heights |
E781862
|
entity |
| Predicate | identifiesStationOn |
P145062
|
FINISHED |
| Object | New Haven Line |
—
|
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 Haven Line | Statement: [MNR Noroton Heights, identifiesStationOn, New Haven Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesStationOn Context triple: [MNR Noroton Heights, identifiesStationOn, New Haven Line]
-
A.
identifiesStationInDatabase
Indicates that an entity is recognized and matched as a specific station within a database system.
-
B.
identifiesPhysicalStation
Indicates that one entity specifies or designates the particular physical station associated with another entity.
-
C.
isStationOf
Indicates that a given location functions as a station (e.g., transport or service hub) associated with or serving a particular system, line, route, or organization.
-
D.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
E.
identifiesStationWithinLine
chosen
Indicates that a specific station is recognized as belonging to, or located within, a particular transit line.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 8:35 p.m.