Triple

T4878611
Position Surface form Disambiguated ID Type / Status
Subject Montague Street Tunnel E109266 entity
Predicate closedForHurricaneSandyRepairs P28319 FINISHED
Object 2013-08-02 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: 2013-08-02 | Statement: [Montague Street Tunnel, closedForHurricaneSandyRepairs, 2013-08-02]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: closedForHurricaneSandyRepairs
Context triple: [Montague Street Tunnel, closedForHurricaneSandyRepairs, 2013-08-02]
  • A. closedFor
    Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
  • B. closedAsNavyYard
    Indicates that a facility or site was officially closed in its capacity as a navy yard.
  • C. hasReconstructionWork chosen
    Indicates that an entity is undergoing, has undergone, or is associated with reconstruction or restoration work.
  • D. closedDuring
    Indicates that an entity is not open or available for use during a specified time period or under certain conditions.
  • E. closedUnder
    Indicates that applying a specified operation to elements within a set always produces a result that is also an element of that same set.
  • 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.