Triple
T4281579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palestine: Peace Not Apartheid |
E97161
|
entity |
| Predicate | positionOnConflict |
P20467
|
FINISHED |
| Object | supports negotiated 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: supports negotiated peace agreement | Statement: [Palestine: Peace Not Apartheid, positionOnConflict, supports negotiated peace agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnConflict Context triple: [Palestine: Peace Not Apartheid, positionOnConflict, supports negotiated peace agreement]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
previousConflict
Indicates that a conflict or dispute occurred between the entities at some earlier time prior to the current context.
-
C.
positionUse
Indicates how a particular position or role is utilized or functionally applied within a given context.
-
D.
positionChange
Indicates a change in an entity’s spatial or positional state from one location or configuration to another.
-
E.
positionOnIssue
chosen
Indicates the stance or viewpoint an entity holds regarding a specific issue or topic.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3503938f481909505e0a322dd2b6c |
completed | March 12, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.