Triple

T33521582
Position Surface form Disambiguated ID Type / Status
Subject ME 135 E858516 entity
Predicate openToPublicTraffic P18212 FINISHED
Object yes 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: yes | Statement: [ME 135, openToPublicTraffic, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: openToPublicTraffic
Context triple: [ME 135, openToPublicTraffic, yes]
  • A. openToPublicAs
    Indicates that something (such as a place, resource, or event) is made accessible or available for use, entry, or participation by the general public in a specified capacity or role.
  • B. openedForThroughTraffic
    Indicates that a route or segment is available and accessible for vehicles to pass through (not just for local access), allowing continuous through traffic.
  • C. openedToPassengerTraffic
    Indicates that a transportation facility or route began operating and accepting passengers for regular use.
  • D. openedToCivilianTraffic
    Indicates that a previously restricted or closed route, facility, or infrastructure has been made accessible for use by civilian (non-military) traffic.
  • E. openedForPublic chosen
    Indicates that something has been made accessible or available for use, entry, or participation by the general public.
  • 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_69f349781c6c819082c516b260efe7e2 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6f8164698819090c1b471f1caa4c6 completed May 3, 2026, 7:24 a.m.
PD Predicate disambiguation batch_69f6f6619404819084662aef1238261c completed May 3, 2026, 7:16 a.m.
Created at: May 1, 2026, 1:39 a.m.