Triple
T31265610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAC |
E797244
|
entity |
| Predicate | announcedPlanFor |
P156806
|
FINISHED |
| Object | new elections under its supervision |
—
|
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: new elections under its supervision | Statement: [SAC, announcedPlanFor, new elections under its supervision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedPlanFor Context triple: [SAC, announcedPlanFor, new elections under its supervision]
-
A.
planningAnnounced
chosen
Indicates that an intention or plan for a future action or event has been formally communicated or made public.
-
B.
announcedFor
Indicates that one entity has been publicly declared or made known in connection with, or on behalf of, another entity.
-
C.
announcedThat
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
D.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
E.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:12 p.m.