Triple

T1139909
Position Surface form Disambiguated ID Type / Status
Subject President of Chile E23425 entity
Predicate hasOath P16811 FINISHED
Object oath to uphold the Constitution of Chile 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: oath to uphold the Constitution of Chile | Statement: [President of Chile, hasOath, oath to uphold the Constitution of Chile]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOath
Context triple: [President of Chile, hasOath, oath to uphold the Constitution of Chile]
  • A. hasOathTo chosen
    Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
  • B. oathTakenBy
    Indicates that an oath or formal promise has been made by a specific entity.
  • C. hasSwornStatus
    Indicates that an entity is formally bound by an oath or sworn commitment, reflecting an official or pledged status in relation to another entity or role.
  • D. oathSwornBefore
    Indicates that an oath or solemn promise has been formally declared in the presence of a specified person, group, or authority.
  • E. oath
    Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
  • 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_69a493ef399c8190b04b9146d2314f59 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4bde18d208190848c189b2b8d585f completed March 1, 2026, 10:29 p.m.
PD Predicate disambiguation batch_69a4bb4b52d48190bec2e7ad1cc8efc0 completed March 1, 2026, 10:18 p.m.
Created at: March 1, 2026, 7:44 p.m.