Triple

T37394098
Position Surface form Disambiguated ID Type / Status
Subject Bois Caïman E928799 entity
Predicate hasContestedAspects P81772 FINISHED
Object historicity of details of the 1791 ceremony 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: historicity of details of the 1791 ceremony | Statement: [Bois Caïman, hasContestedAspects, historicity of details of the 1791 ceremony]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasContestedAspects
Context triple: [Bois Caïman, hasContestedAspects, historicity of details of the 1791 ceremony]
  • A. isContestedBecause
    Indicates that something is disputed or challenged due to a specified reason or cause.
  • B. hasControversialAspect chosen
    Indicates that something includes an element, feature, or aspect that is disputed, debated, or likely to cause disagreement or public criticism.
  • C. contestedAs
    Indicates that one entity challenges, disputes, or competes for the status, claim, or position held by another entity.
  • D. contestedBy
    Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
  • E. areContestedIn
    Indicates that something is the subject of dispute, challenge, or competition within a particular context, event, or process.
  • 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_69f76ebb10c481909b54b9dba263e29f completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a037c8efcd4819088c2aeead65d93df completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a13a1308190a202df66f4781855 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:16 p.m.