Triple

T23363535
Position Surface form Disambiguated ID Type / Status
Subject The Barrier E593247 entity
Predicate accessToInteriorVia P143167 FINISHED
Object routes through gaps and glacier tongues at its edge 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: routes through gaps and glacier tongues at its edge | Statement: [The Barrier, accessToInteriorVia, routes through gaps and glacier tongues at its edge]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: accessToInteriorVia
Context triple: [The Barrier, accessToInteriorVia, routes through gaps and glacier tongues at its edge]
  • A. interiorAccess chosen
    Indicates that one entity provides a way to enter or move within the inside space of another entity.
  • B. guardedEntranceTo
    Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
  • C. floorAccess
    Indicates that an entity is permitted to enter or use a specific floor or level within a building or structure.
  • D. hasEntrance
    Indicates that one entity possesses or provides an entry point or access way to another entity or space.
  • E. hasDomeOrRoofAccess
    Indicates that an entity has access to, or the ability to reach or use, a dome or roof area associated with another entity.
  • 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_69e25d2593c88190bcdf4a716a94ccb2 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a0aac4248190a4663ed12aed6856 completed April 29, 2026, 6:09 a.m.
PD Predicate disambiguation batch_69f061c7aaa48190a58ce93f87155ffc completed April 28, 2026, 7:29 a.m.
Created at: April 17, 2026, 5:31 p.m.