Triple
T4448551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyne |
E96348
|
entity |
| Predicate | byElectionTriggeredBy |
P14472
|
FINISHED |
| Object | resignation of Mark Vaile |
—
|
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: resignation of Mark Vaile | Statement: [Lyne, byElectionTriggeredBy, resignation of Mark Vaile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: byElectionTriggeredBy Context triple: [Lyne, byElectionTriggeredBy, resignation of Mark Vaile]
-
A.
byElectionReason
chosen
Indicates the reason or cause for which a by-election is being held.
-
B.
reElectionOf
Indicates that an entity is being elected again to a position or office they have previously held.
-
C.
electedWith
Indicates that one entity attained an elected position or office together with, or as part of the same electoral outcome as, another entity.
-
D.
requiresElectionBy
Indicates that one entity can only assume a role, status, or condition if it is chosen through a formal election process conducted by another entity or group.
-
E.
associatedWithElection
Indicates a relationship where something is connected or related to a specific election, such as being part of its process, context, or outcomes.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d45b748190b09b7067fc6279b0 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.