Triple

T4078892
Position Surface form Disambiguated ID Type / Status
Subject Greenlandian E87429 entity
Predicate upperBoundaryDefinition P52351 FINISHED
Object climatic event around 8.2 ka BP 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: climatic event around 8.2 ka BP | Statement: [Greenlandian, upperBoundaryDefinition, climatic event around 8.2 ka BP]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: upperBoundaryDefinition
Context triple: [Greenlandian, upperBoundaryDefinition, climatic event around 8.2 ka BP]
  • A. upperLimit
    Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
  • B. endBoundaryDefinedBy chosen
    Indicates that the endpoint or final limit of one entity is determined, marked, or delimited by another entity.
  • C. isUpperBoundFor
    Indicates that one value is greater than or equal to every element in a given set or collection, serving as an upper limit for them.
  • D. outerLimitDefinedFrom
    Indicates that the outer boundary or maximum extent of one entity is determined or specified based on another entity.
  • E. hasLowerBoundaryDefinedBy
    Indicates that one entity’s lower limit, edge, or boundary is specified or determined by 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_69aed9435cf48190ad1da737c962d19d completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefc4e95b08190bd1ee8f6d3a9613c completed March 9, 2026, 4:58 p.m.
PD Predicate disambiguation batch_69aef9082c2081908474f082a49bebc8 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:39 p.m.