Triple
T36400722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abyei |
E896615
|
entity |
| Predicate | plannedButNotImplemented |
P117074
|
FINISHED |
| Object | referendum on final status |
—
|
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: referendum on final status | Statement: [Abyei, plannedButNotImplemented, referendum on final status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedButNotImplemented Context triple: [Abyei, plannedButNotImplemented, referendum on final status]
-
A.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
B.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
-
C.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
D.
plannedFeature
Indicates that a particular feature is intended or scheduled to be developed or implemented in the future.
-
E.
plannedButUnrealizedEntry
chosen
Indicates that an entry was intended or scheduled to occur but ultimately did not take place or was never realized.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 3, 2026, 4:10 p.m.