Triple
T3841389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatton |
E93456
|
entity |
| Predicate | 1997ElectionType |
P19539
|
FINISHED |
| Object | independent candidate victory |
—
|
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: independent candidate victory | Statement: [Tatton, 1997ElectionType, independent candidate victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1997ElectionType Context triple: [Tatton, 1997ElectionType, independent candidate victory]
-
A.
hasElectionType
chosen
Indicates the specific category or kind of election associated with a given electoral event or process.
-
B.
premierElectedBy
Indicates that a premier attains office through an election conducted or decided by a specified person, group, or body.
-
C.
appliesToElectionType
Indicates that a rule, condition, or attribute is relevant or applicable to a specific type or category of election.
-
D.
electionsAdministeredBy
Indicates that the specified elections are organized, managed, or overseen by the given administrative authority or body.
-
E.
electoralSystemConcerned
Indicates that something is related to, affected by, or focused on a particular electoral system.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb235088190b115623e54ea2ab1 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.