Triple
T19731761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Democratic Alliance (support in 1980 election) |
E473870
|
entity |
| Predicate | backedIncumbent |
P137128
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Democratic Alliance (support in 1980 election), backedIncumbent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backedIncumbent Context triple: [Democratic Alliance (support in 1980 election), backedIncumbent, true]
-
A.
incumbent
Indicates that an entity currently holds a particular position, office, or role at the present time.
-
B.
targetedIncumbent
Indicates that an action, strategy, or effort was specifically directed at an existing office-holder or current position-holder.
-
C.
incumbentOutcome
Indicates the result or consequence experienced by the current officeholder or position-holder in a given event or context.
-
D.
incumbentBeforeElection
Indicates that the subject was already holding the relevant office or position prior to the specified election.
-
E.
lastIncumbent
Indicates that the subject is the most recent person or entity to have held a particular position, office, or role before the current one.
- F. None of above. chosen
Provenance (4 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649fd18148190a6e85b2be0069dde |
completed | April 20, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:47 p.m.