Triple
T36690076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golda Meir Government |
E905930
|
entity |
| Predicate | oversawConflict |
P45010
|
FINISHED |
| Object | Yom Kippur 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: Yom Kippur War | Statement: [Golda Meir Government, oversawConflict, Yom Kippur War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oversawConflict Context triple: [Golda Meir Government, oversawConflict, Yom Kippur War]
-
A.
militaryConflictOversaw
chosen
Indicates that one party had authoritative oversight or command responsibility over a military conflict involving another party.
-
B.
facedConflictOver
Indicates that two or more entities experienced opposition, dispute, or tension concerning a particular issue, resource, or situation.
-
C.
conflictBeganOver
Indicates that a conflict was initiated due to or in response to a particular cause, issue, or trigger.
-
D.
conflictForControlOf
Indicates a struggle or contest between parties to gain dominance, authority, or decision-making power over something.
-
E.
hasPartOfConflict
Indicates that one conflict includes another conflict as a constituent or subordinate part of it.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.