Triple

T38625269
Position Surface form Disambiguated ID Type / Status
Subject Glarus thrust E936987 entity
Predicate hasMaximumDisplacement P84064 FINISHED
Object several kilometers 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: several kilometers | Statement: [Glarus thrust, hasMaximumDisplacement, several kilometers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMaximumDisplacement
Context triple: [Glarus thrust, hasMaximumDisplacement, several kilometers]
  • A. hasMaxDisplacement chosen
    Indicates the maximum distance or extent to which something can move or be displaced from its original position.
  • B. maximumHorizontalDisplacement
    Indicates the greatest distance an entity can or does move horizontally from a reference point or along a horizontal axis.
  • C. hasDisplacement
    Indicates a relationship where an entity experiences or is assigned a change in position or location from an initial point to a final point.
  • D. governingDisplacementLimit
    Indicates the maximum allowable amount or extent of displacement that governs or constrains a particular motion, deformation, or positional change.
  • E. displacementRange
    Indicates the minimum and maximum extent of positional change or movement that an entity can undergo or exhibits.
  • 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_69f76ed403208190b862dc795171353f completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a037c9141dc819098d7fcc36e69882c completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a2026248190b894436a578d79ac completed May 12, 2026, 7:06 p.m.
Created at: May 3, 2026, 4:32 p.m.