Triple
T23207624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Committee on Electoral Reform |
E580502
|
entity |
| Predicate | consideredCurrentSystem |
P151361
|
FINISHED |
| Object | first‑past‑the‑post |
—
|
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: first‑past‑the‑post | Statement: [Special Committee on Electoral Reform, consideredCurrentSystem, first‑past‑the‑post]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredCurrentSystem Context triple: [Special Committee on Electoral Reform, consideredCurrentSystem, first‑past‑the‑post]
-
A.
currentSystem
Indicates that an entity is the system or configuration that is presently active or in use.
-
B.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
C.
consideredPlatform
Indicates that one entity is regarded or treated as a platform (e.g., a base, medium, or environment) for another entity or activity.
-
D.
inSameSystemAs
Indicates that two entities are located within or belong to the same overarching system or framework.
-
E.
isInSystem
Indicates that one entity is located within, belongs to, or is contained by a particular system.
- 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907d8be08190a100d99efaff9964 |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:07 p.m.