Triple

T10035843
Position Surface form Disambiguated ID Type / Status
Subject Marilyn (mountain) E204966 entity
Predicate heightCriterion P92042 FINISHED
Object no minimum absolute height 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: no minimum absolute height | Statement: [Marilyn (mountain), heightCriterion, no minimum absolute height]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heightCriterion
Context triple: [Marilyn (mountain), heightCriterion, no minimum absolute height]
  • A. heightClass
    Indicates the categorical height level or range to which an entity is assigned (e.g., short, medium, tall).
  • B. heightReference
    Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
  • C. hasHeight
    Indicates that one entity possesses a specific vertical measurement or stature.
  • D. heightDescription
    Indicates how tall an entity is, typically expressed in descriptive or qualitative terms rather than a precise measurement.
  • E. heightAboveSurroundings
    Indicates that an entity’s vertical position or elevation is higher than that of its immediate surrounding area.
  • 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_69ca834d77188190ad645e33e8ca3200 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cdce4bb3408190ac5dae4718ef7cad completed April 2, 2026, 2:02 a.m.
PD Predicate disambiguation batch_69cd4b8638508190b22acc65500ec7d6 completed April 1, 2026, 4:44 p.m.
PDg Predicate description generation batch_69cd4fed19d481909d2c7ff1114664b6 completed April 1, 2026, 5:03 p.m.
Created at: March 30, 2026, 8:55 p.m.