Triple

T3968708
Position Surface form Disambiguated ID Type / Status
Subject Indian Head E92276 entity
Predicate hasGeologicalForm P4015 FINISHED
Object rocky headland 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: rocky headland | Statement: [Indian Head, hasGeologicalForm, rocky headland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGeologicalForm
Context triple: [Indian Head, hasGeologicalForm, rocky headland]
  • A. geologicalFormation chosen
    Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
  • B. hasGeologicalSignificance
    Indicates that something possesses notable importance or relevance within a geological context, such as Earth’s structure, history, or processes.
  • C. hasGeologicalUnit
    Indicates that an entity is associated with or contains a specific geological unit, such as a rock layer, formation, or stratigraphic unit.
  • D. geologicalStatus
    Indicates the current geological condition or classification of an entity, such as its formation state, activity level, or structural status within the Earth’s crust.
  • E. geologicType
    Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
  • 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_69aed96624188190ac8c45bb57ab72b5 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefaca33e4819091957c7915857a42 completed March 9, 2026, 4:52 p.m.
PD Predicate disambiguation batch_69aef8f252b081909749d40440d372b2 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:32 p.m.