Triple
T26026249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q70 SBS to LaGuardia Airport |
E647298
|
entity |
| Predicate | primarySubwayConnections |
P18378
|
FINISHED |
| Object | E subway service |
—
|
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: E subway service | Statement: [Q70 SBS to LaGuardia Airport, primarySubwayConnections, E subway service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySubwayConnections Context triple: [Q70 SBS to LaGuardia Airport, primarySubwayConnections, E subway service]
-
A.
hasUndergroundConnections
Indicates that one entity is linked to another through subterranean or hidden passageways, networks, or channels.
-
B.
nearbyMainlineConnection
Indicates that one entity has a mainline connection located in close physical proximity to another entity.
-
C.
subwayLine
chosen
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
D.
connectsSubwayDivisions
Indicates that one entity serves as a link or junction that joins or integrates multiple subway divisions into a connected system.
-
E.
subwayServices
Indicates that one entity provides or operates subway transportation services for another entity or area.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 22, 2026, 9:05 a.m.