Triple
T29384902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Six-Point Peace Plan |
E745224
|
entity |
| Predicate | point |
P17093
|
FINISHED |
| Object | no recourse to the use of force |
—
|
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: no recourse to the use of force | Statement: [Six-Point Peace Plan, point, no recourse to the use of force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: point Context triple: [Six-Point Peace Plan, point, no recourse to the use of force]
-
A.
points
Indicates that one entity directs attention, focus, or a physical/abstract indication toward another entity or location.
-
B.
pointDefinition
chosen
Indicates that one entity serves as the defining description or specification of a particular point in another entity.
-
C.
anchorPoint
Indicates a fixed reference position used to attach, align, or position one entity relative to another.
-
D.
pointSource
Indicates that an entity acts as a localized origin or emitter of some quantity (such as light, sound, or radiation) concentrated at a single point in space.
-
E.
interactionPoint
Indicates a specific location or moment where two or more entities come into contact or engage with each other.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 2:38 p.m.