Triple
T29384940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarkozy Plan |
E745225
|
entity |
| Predicate | proposedDuringConflict |
P49719
|
FINISHED |
| Object | 2008 South Ossetia war |
—
|
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: 2008 South Ossetia war | Statement: [Sarkozy Plan, proposedDuringConflict, 2008 South Ossetia war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedDuringConflict Context triple: [Sarkozy Plan, proposedDuringConflict, 2008 South Ossetia war]
-
A.
usedByDuringConflict
Indicates that one entity made practical use of another entity specifically in the context of a particular conflict or war.
-
B.
implementedDuringConflict
chosen
Indicates that an action, policy, or measure was carried out while an active conflict or war was ongoing.
-
C.
conflictPeriod
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
D.
previousConflict
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
-
E.
existedDuringConflict
Indicates that an entity was present or active for some or all of the duration of a specified conflict.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 28, 2026, 2:38 p.m.