Triple

T5961336
Position Surface form Disambiguated ID Type / Status
Subject Eurasia Tunnel E132643 entity
Predicate hasEmergencyExit P31156 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: [Eurasia Tunnel, hasEmergencyExit, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEmergencyExit
Context triple: [Eurasia Tunnel, hasEmergencyExit, yes]
  • A. hasEmergencyExits chosen
    Indicates that an entity is equipped with designated emergency exits for use during urgent or hazardous situations.
  • B. numberOfEmergencyExits
    Indicates the quantity of emergency exits associated with an entity or location.
  • C. hasEmergencyWalkway
    Indicates that there is a designated emergency walkway available or present between the related entities.
  • D. accessibleExit
    Indicates that an exit is designed and configured to be usable by people with disabilities, meeting accessibility requirements.
  • E. hasEmergencyStairwells
    Indicates that an entity is equipped with one or more stairwells specifically designated and constructed for use during emergencies.
  • 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_69c0086c2364819091e9fe2f58fa2517 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c03fb7f8a88190a8bd45208bda4a03 completed March 22, 2026, 7:15 p.m.
PD Predicate disambiguation batch_69c0335a635881909c58c1ef0f97f1e8 completed March 22, 2026, 6:22 p.m.
Created at: March 22, 2026, 4:02 p.m.