Triple

T16467933
Position Surface form Disambiguated ID Type / Status
Subject Wellington E399981 entity
Predicate hasEmergencyEgress P31156 FINISHED
Object stairways 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: stairways | Statement: [Wellington, hasEmergencyEgress, stairways]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEmergencyEgress
Context triple: [Wellington, hasEmergencyEgress, stairways]
  • A. hasEmergencyExits chosen
    Indicates that an entity is equipped with designated emergency exits for use during urgent or hazardous situations.
  • B. hasEmergencyWalkway
    Indicates that there is a designated emergency walkway available or present between the related entities.
  • C. hasEmergencyLevel
    Indicates that an entity is associated with a specific degree or severity of emergency status.
  • D. hasEmergencySystems
    Indicates that the subject is equipped with or includes systems designed to detect, respond to, or manage emergency situations.
  • E. hasNearbyExit
    Indicates that one entity has an exit located close to it in space or distance.
  • 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_69d87f2dac988190b74d6e185fa88ba4 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32dcd707081908fb7ca91a8c09e0a completed April 18, 2026, 7:07 a.m.
PD Predicate disambiguation batch_69e227048d608190a4205eae3117629a completed April 17, 2026, 12:26 p.m.
Created at: April 10, 2026, 5:11 a.m.