Triple

T25581996
Position Surface form Disambiguated ID Type / Status
Subject Anton Anderson Memorial Tunnel E641268 entity
Predicate hasSafetyRestriction P157221 FINISHED
Object speed limits enforced 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: speed limits enforced | Statement: [Anton Anderson Memorial Tunnel, hasSafetyRestriction, speed limits enforced]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSafetyRestriction
Context triple: [Anton Anderson Memorial Tunnel, hasSafetyRestriction, speed limits enforced]
  • A. hasMarketingRestrictions
    Indicates that there are specific limitations or conditions imposed on how something may be marketed or promoted.
  • B. hasHumanUseRestriction chosen
    Indicates that there is a limitation or condition on how something may be used by humans.
  • C. mayHaveRestriction
    Indicates that an entity can be subject to one or more limitations, conditions, or constraints, though such restrictions are not necessarily present.
  • D. hasPerformanceMediumRestriction
    Indicates that there is a limitation or condition on the medium or format through which a performance may be presented or delivered.
  • E. hadRestrictionsOn
    Indicates that one entity imposed or was subject to specific limitations, rules, or constraints regarding another entity or activity.
  • 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_69e75dc42b588190a98b58e0df359674 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f62d89b89c8190afb372a8172111e7 completed May 2, 2026, 4:59 p.m.
PD Predicate disambiguation batch_69f62c1379f08190836c3e02b0c892df completed May 2, 2026, 4:53 p.m.
Created at: April 21, 2026, 4:13 p.m.