Triple
T16630762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comprehensive Peace Agreement |
E404071
|
entity |
| Predicate | conflictDurationAddressed |
P28865
|
FINISHED |
| Object | 1983–2005 |
—
|
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: 1983–2005 | Statement: [Comprehensive Peace Agreement, conflictDurationAddressed, 1983–2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictDurationAddressed Context triple: [Comprehensive Peace Agreement, conflictDurationAddressed, 1983–2005]
-
A.
conflictPeriod
chosen
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
B.
addressedConflictWith
Indicates that one entity has taken action to confront, manage, or resolve a conflict involving another entity.
-
C.
conflictStartTime
Indicates the specific point in time at which a conflict between entities begins.
-
D.
facedConflictOver
Indicates that two or more entities experienced opposition, dispute, or tension concerning a particular issue, resource, or situation.
-
E.
conflictDescribedIn
Indicates that a particular conflict is documented, detailed, or discussed within a specified information source or description.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e378e5d4448190bfb1b6157bbe5285 |
completed | April 18, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.