Triple

T8113510
Position Surface form Disambiguated ID Type / Status
Subject Cross of Valour E189412 entity
Predicate createdToReplace P81350 FINISHED
Object use of British bravery decorations for Canadians 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: use of British bravery decorations for Canadians | Statement: [Cross of Valour, createdToReplace, use of British bravery decorations for Canadians]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: createdToReplace
Context triple: [Cross of Valour, createdToReplace, use of British bravery decorations for Canadians]
  • A. createdTo
    Indicates that one entity was brought into existence, produced, or designed specifically for the purpose, use, or function of another entity.
  • B. placedBy
    Indicates that one entity was positioned, set, or put in a location or context by another entity.
  • C. replacedBecause
    Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
  • D. seeksToReplace
    Indicates an intention or effort by one entity to take over the role, function, or position currently held by another entity.
  • E. replacedDuring
    Indicates that one entity took the place of another entity during a specified time period or interval.
  • 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_69ca82baad008190ab2859712b9b1607 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb4664fef881908b0dc7b158aca398 completed March 31, 2026, 3:58 a.m.
PD Predicate disambiguation batch_69cb368e7f4c81909aabd7716f0de79d completed March 31, 2026, 2:50 a.m.
PDg Predicate description generation batch_69cb46635424819085d086972b264280 completed March 31, 2026, 3:58 a.m.
Created at: March 30, 2026, 5:32 p.m.