Triple

T35882190
Position Surface form Disambiguated ID Type / Status
Subject United States (during early Iran–Iraq War period) E1037539 entity
Predicate usedPolicyFramework P25238 FINISHED
Object Carter Doctrine 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: Carter Doctrine | Statement: [United States (during early Iran–Iraq War period), usedPolicyFramework, Carter Doctrine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedPolicyFramework
Context triple: [United States (during early Iran–Iraq War period), usedPolicyFramework, Carter Doctrine]
  • A. usedPolicy
    Indicates that an entity applied or followed a particular policy in carrying out an action or decision.
  • B. policyFramework chosen
    Indicates the overarching set of principles, rules, and guidelines that govern how decisions and actions are structured and carried out within a particular domain or context.
  • C. establishedPolicy
    Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
  • D. usesPolicyModel
    Indicates that one entity applies, relies on, or operates according to a particular policy model.
  • E. implementedPolicy
    Indicates that a particular policy has been put into effect or carried out by an entity.
  • 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_69f76e1f4d748190bb55594d8441d70e completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7ac23d1388190bdf9628b294943bd completed May 3, 2026, 8:12 p.m.
PD Predicate disambiguation batch_69f7ab734d848190a84f9b8c3a952b75 completed May 3, 2026, 8:09 p.m.
Created at: May 3, 2026, 4:06 p.m.