Triple
T1455114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annapolis Conference |
E31379
|
entity |
| Predicate | soughtOutcome |
P22603
|
FINISHED |
| Object | comprehensive peace agreement |
—
|
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: comprehensive peace agreement | Statement: [Annapolis Conference, soughtOutcome, comprehensive peace agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soughtOutcome Context triple: [Annapolis Conference, soughtOutcome, comprehensive peace agreement]
-
A.
laterSought
Indicates that one entity attempted to obtain, pursue, or request another entity at a subsequent time relative to some prior reference point.
-
B.
soughtTitle
Indicates that an entity actively pursued or attempted to obtain a particular title or position.
-
C.
initialOutcome
Indicates the result or state that first occurs at the beginning of a process, event, or interaction, before any subsequent changes or outcomes.
-
D.
outcomeType
chosen
Indicates the specific category or nature of the result produced by an event, process, or action.
-
E.
isSoughtBy
Indicates that one entity is actively being searched for, pursued, or desired by another entity.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c57fead881909a47188ce7312406 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.