Triple
T38323861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPA 2006 |
E1036728
|
entity |
| Predicate | endedConflictDuration |
P28865
|
FINISHED |
| Object | 1996–2006 |
—
|
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: 1996–2006 | Statement: [CPA 2006, endedConflictDuration, 1996–2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedConflictDuration Context triple: [CPA 2006, endedConflictDuration, 1996–2006]
-
A.
endedConflict
Indicates that a previously ongoing conflict between entities has been brought to an end.
-
B.
endedConflictPhase
Indicates that a particular phase or stage within a broader conflict has come to an end.
-
C.
conflictPeriod
chosen
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
D.
statusDuringConflict
Indicates the role, condition, or standing an entity held throughout a specified conflict or period of hostilities.
-
E.
disputeDuration
Indicates the length of time over which a dispute persists or remains unresolved between parties.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:30 p.m.