Triple
T15794108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian presidential election 2008 (attempted) |
E382931
|
entity |
| Predicate | reasonForUnrealizedStatus |
P30133
|
FINISHED |
| Object | political obstacles |
—
|
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: political obstacles | Statement: [Russian presidential election 2008 (attempted), reasonForUnrealizedStatus, political obstacles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForUnrealizedStatus Context triple: [Russian presidential election 2008 (attempted), reasonForUnrealizedStatus, political obstacles]
-
A.
reasonForStatus
chosen
Indicates the explanation or cause underlying a particular state or condition.
-
B.
reasonForUnorganizedStatus
Indicates the explanation or cause for why something is in an unorganized or non-structured state.
-
C.
stabilityReason
Indicates the factor, condition, or cause that accounts for why something remains stable or unchanged.
-
D.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
E.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4db55308190875a04f982c44cea |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.