Triple
T1086204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Agenda for Peace |
E24055
|
entity |
| Predicate | keyTermUsed |
P2309
|
FINISHED |
| Object | preventive diplomacy |
—
|
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: preventive diplomacy | Statement: [An Agenda for Peace, keyTermUsed, preventive diplomacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyTermUsed Context triple: [An Agenda for Peace, keyTermUsed, preventive diplomacy]
-
A.
keyTerm
chosen
Indicates that a term functions as a primary or central concept within a given context or information structure.
-
B.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
-
C.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
D.
keySymbol
Indicates that one entity serves as the symbolic representation or notation used to denote another entity as a key.
-
E.
coinedTerm
Indicates that an entity originated and introduced a particular term or expression into use.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b963161081908a523c8d63871652 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.