Triple

T37534893
Position Surface form Disambiguated ID Type / Status
Subject UN Security Council Resolution 298 E933168 entity
Predicate concernsWar P106867 FINISHED
Object Six-Day War NE NERFINISHED

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: Six-Day War | Statement: [UN Security Council Resolution 298, concernsWar, Six-Day War]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: concernsWar
Context triple: [UN Security Council Resolution 298, concernsWar, Six-Day War]
  • A. concernsWarBetween chosen
    Indicates a relationship where something (such as a statement, document, or event) is about or pertains to a war occurring between two or more parties.
  • B. strategicConcernFor
    Indicates a relationship where one entity considers another entity’s situation, actions, or outcomes important for its own long-term goals, risks, or strategic interests.
  • C. concern
    Indicates that one entity is about, relates to, or is of interest or importance to another entity.
  • D. concernedSee
    Indicates that one entity looks at or observes another with a sense of worry, care, or concern.
  • E. protectionConcerns
    Indicates that there are identified risks, threats, or vulnerabilities affecting the safety, rights, or well-being of an entity that may require protective action or safeguards.
  • 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_69f76ec999288190ae26ec7b6aea7046 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbb9e8108c8190ae1c7940b1677e95 completed May 6, 2026, 10 p.m.
PD Predicate disambiguation batch_69fbb141605c8190b9c27d70352522db completed May 6, 2026, 9:23 p.m.
Created at: May 3, 2026, 4:17 p.m.