Triple

T12743933
Position Surface form Disambiguated ID Type / Status
Subject Chauvet-Pont-d’Arc Cave E304554 entity
Predicate hasEntranceElevation P106679 FINISHED
Object approximately 185 meters above sea level 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: approximately 185 meters above sea level | Statement: [Chauvet-Pont-d’Arc Cave, hasEntranceElevation, approximately 185 meters above sea level]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEntranceElevation
Context triple: [Chauvet-Pont-d’Arc Cave, hasEntranceElevation, approximately 185 meters above sea level]
  • A. entranceHeight
    Indicates the vertical measurement of how tall an entrance is.
  • B. hasEntranceStructure
    Indicates that one entity possesses or is associated with a specific physical structure that serves as its entrance.
  • C. hasEntrance
    Indicates that one entity possesses or provides an entry point or access way to another entity or space.
  • D. hasElevatorConnection
    Indicates that there is a direct elevator-based connection or access route between two locations or entities.
  • E. hasEntranceOn
    Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
  • F. None of above. chosen

Provenance (4 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_69d7bdf1426c8190a4402e1c4cdec33a completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96d89ea70819098c470344f172167 completed April 10, 2026, 9:37 p.m.
PD Predicate disambiguation batch_69d96406e97c8190b79081039847115c completed April 10, 2026, 8:56 p.m.
PDg Predicate description generation batch_69d96d87078c819083ea724238992204 completed April 10, 2026, 9:37 p.m.
Created at: April 9, 2026, 5:26 p.m.