Triple

T4955249
Position Surface form Disambiguated ID Type / Status
Subject Military Armistice Commission E111265 entity
Predicate statusOfConflict P47615 FINISHED
Object operates in absence of a formal peace treaty 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: operates in absence of a formal peace treaty | Statement: [Military Armistice Commission, statusOfConflict, operates in absence of a formal peace treaty]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: statusOfConflict
Context triple: [Military Armistice Commission, statusOfConflict, operates in absence of a formal peace treaty]
  • A. statusDuringConflict
    Indicates the role, condition, or standing an entity held throughout a specified conflict or period of hostilities.
  • B. conflictRelatedStatus chosen
    Indicates a status or condition that is directly associated with, affected by, or resulting from a conflict.
  • C. postConflictStatus
    Indicates the condition or circumstances of an entity after a conflict or dispute has concluded.
  • D. conflictStance
    Indicates a party’s position, attitude, or alignment regarding a particular conflict or dispute.
  • E. endedConflict
    Indicates that a previously ongoing conflict between entities has been brought to an end.
  • 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_69bd4418390c8190b7e9766a2512ce55 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd71babb44819085b4cd4864433e79 completed March 20, 2026, 4:11 p.m.
PD Predicate disambiguation batch_69bd6c3beb008190852fd6150813b252 completed March 20, 2026, 3:48 p.m.
Created at: March 20, 2026, 1:32 p.m.