Triple
T22771648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeast Corridor at New Haven |
E563572
|
entity |
| Predicate | connectsServiceType |
P149668
|
FINISHED |
| Object | intercity rail |
—
|
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: intercity rail | Statement: [Northeast Corridor at New Haven, connectsServiceType, intercity rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsServiceType Context triple: [Northeast Corridor at New Haven, connectsServiceType, intercity rail]
-
A.
connectsDeviceType
Indicates a relationship where one entity is associated with or linked to a specific type or category of device.
-
B.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
C.
connectsDestinationType
Indicates that one entity serves as a connection or link specifically to a destination of a given type.
-
D.
telecommunicationsType
Indicates the specific category or mode of telecommunications service or technology associated with an entity.
-
E.
connectsWorks
Indicates a relationship where one work serves to link, bridge, or associate two or more other works.
- 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b5e77d081909ea58d55c240662c |
completed | April 29, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:27 p.m.