Triple

T742191
Position Surface form Disambiguated ID Type / Status
Subject Holocene E15266 entity
Predicate hasFormalStatus P18869 FINISHED
Object formal chronostratigraphic unit 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: formal chronostratigraphic unit | Statement: [Holocene, hasFormalStatus, formal chronostratigraphic unit]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFormalStatus
Context triple: [Holocene, hasFormalStatus, formal chronostratigraphic unit]
  • A. hasInformalStatus
    Indicates that an entity holds a non-official, casual, or unofficial standing or role in relation to another entity.
  • B. hasLegalStatus
    Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
  • C. isFormalizedBy
    Indicates that something is given a defined, structured, or official form through a specific method, process, or representation.
  • D. areOfficialIn
    Indicates that an entity holds an official role, position, or capacity within another entity (such as an organization, institution, or jurisdiction).
  • E. hasInfluentialStatus
    Indicates that an entity holds a position, role, or condition that gives it significant influence or impact over others or over outcomes.
  • 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_69a49358aa308190adbc9b5a0a2adcf9 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a60e286c81908787a41cf9b9f150 completed March 1, 2026, 8:48 p.m.
PD Predicate disambiguation batch_69a4a4fdaaf48190985f62acfc069508 completed March 1, 2026, 8:43 p.m.
PDg Predicate description generation batch_69a4a5a35c68819082429755c046e9a7 completed March 1, 2026, 8:46 p.m.
Created at: March 1, 2026, 7:37 p.m.