Triple
T2172164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Iraqi Affairs |
E48449
|
entity |
| Predicate | usesPolicyInstruments |
P1652
|
FINISHED |
| Object | diplomatic engagement |
—
|
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: diplomatic engagement | Statement: [Office of Iraqi Affairs, usesPolicyInstruments, diplomatic engagement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPolicyInstruments Context triple: [Office of Iraqi Affairs, usesPolicyInstruments, diplomatic engagement]
-
A.
usesPolicyModel
Indicates that one entity applies, relies on, or operates according to a particular policy model.
-
B.
usesMaterialsPolicy
Indicates that an entity follows, applies, or is governed by a specified policy regarding the use of materials.
-
C.
usesPrinciple
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
D.
issuesPolicyOn
Indicates that an authority or organization formally creates, approves, or enacts a policy concerning a particular subject or domain.
-
E.
policyTool
chosen
Indicates that an entity is a tool, mechanism, or instrument used to design, implement, or enforce a policy.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.