Triple
T4878612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montague Street Tunnel |
E109266
|
entity |
| Predicate | reopenedAfterSandyRepairs |
P34772
|
FINISHED |
| Object | 2014-09-15 |
—
|
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: 2014-09-15 | Statement: [Montague Street Tunnel, reopenedAfterSandyRepairs, 2014-09-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAfterSandyRepairs Context triple: [Montague Street Tunnel, reopenedAfterSandyRepairs, 2014-09-15]
-
A.
repairedIn
Indicates that an item or object underwent repair within a specified location or during a particular time period.
-
B.
reopenedAfterRedevelopment
Indicates that a place or facility was closed for redevelopment and subsequently opened again once the redevelopment was completed.
-
C.
hasReconstructionWork
Indicates that an entity is undergoing, has undergone, or is associated with reconstruction or restoration work.
-
D.
reopenedAfter
chosen
Indicates that an entity was closed or inactive and then opened or made active again following a specified prior event or time.
-
E.
reconstructedAfter
Indicates that one entity has been rebuilt, restored, or reassembled following the occurrence or existence of another entity or event.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dbd69d48190a8397d67af8f5fc8 |
completed | March 20, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.