Triple
T28048699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Artery corridor |
E708757
|
entity |
| Predicate | tunnelSectionName |
P48329
|
FINISHED |
| Object | Thomas P. O’Neill Jr. Tunnel |
—
|
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: Thomas P. O’Neill Jr. Tunnel | Statement: [Central Artery corridor, tunnelSectionName, Thomas P. O’Neill Jr. Tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tunnelSectionName Context triple: [Central Artery corridor, tunnelSectionName, Thomas P. O’Neill Jr. Tunnel]
-
A.
tunnelName
chosen
Indicates the name assigned to a specific tunnel in the relationship or data model.
-
B.
operatorOfTunnelSection
Indicates that an entity is responsible for operating or managing a specific section of a tunnel.
-
C.
tunnelNamedAfter
Indicates that a tunnel bears the name of a particular person, place, event, or entity in whose honor or reference it is designated.
-
D.
hasTunnelSections
Indicates that an entity includes or is composed of multiple distinct tunnel segments or portions.
-
E.
tunnelLocation
Indicates that one entity is the location or site where a tunnel is situated or passes through in relation to another 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:31 p.m.