Triple
T31265609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAC |
E797244
|
entity |
| Predicate | formedNewBody |
P7724
|
FINISHED |
| Object | military-appointed Union Election Commission |
—
|
NE NERFINISHED |
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: military-appointed Union Election Commission | Statement: [SAC, formedNewBody, military-appointed Union Election Commission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedNewBody Context triple: [SAC, formedNewBody, military-appointed Union Election Commission]
-
A.
newBody
Indicates that an entity has acquired or been assigned a new physical form, structure, or body.
-
B.
createdBody
Indicates that one entity brought another entity into existence or produced it as a result of its actions.
-
C.
publicBody
Indicates that an entity functions as a governmental or publicly controlled organization that performs public duties or services.
-
D.
definedBody
Indicates that one entity serves as the formal specification, content, or body definition of another entity.
-
E.
establishedBody
chosen
Indicates that an entity created, founded, or formally set up another entity, such as an organization, institution, or governing body.
- 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_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
Created at: April 29, 2026, 9:12 p.m.