Triple
T6023930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Haven–Springfield Line |
E134127
|
entity |
| Predicate | intercityRole |
P5885
|
FINISHED |
| Object | branch of the Northeast Corridor network |
—
|
LITERAL FINISHED |
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: branch of the Northeast Corridor network | Statement: [New Haven–Springfield Line, intercityRole, branch of the Northeast Corridor network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intercityRole Context triple: [New Haven–Springfield Line, intercityRole, branch of the Northeast Corridor network]
-
A.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
B.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
C.
urbanRole
Indicates the function, status, or role that an entity holds within an urban or city context.
-
D.
railNetworkRole
chosen
Indicates the specific function or responsibility an entity has within a rail network system.
-
E.
intersectionRole
Indicates a role or function that an entity specifically holds at the point where two or more entities, paths, or sets intersect.
- 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_69c008742a5c8190b9cb9c2787a3d8b3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04fbf048081908b0da0cf838730a5 |
completed | March 22, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:07 p.m.