Triple
T19094321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch municipal elections |
E467365
|
entity |
| Predicate | firstElectionHeldIn |
P134349
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Dutch municipal elections, firstElectionHeldIn, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstElectionHeldIn Context triple: [Dutch municipal elections, firstElectionHeldIn, 19th century]
-
A.
firstElectionDate
Indicates the date on which an entity (such as a person or office) participated in or held its first election.
-
B.
firstConstitutionalElectionsHeld
Indicates that the first elections conducted under a new or newly adopted constitution have taken place.
-
C.
firstElectionYear
Indicates the calendar year in which an entity (such as a person, office, or political body) first participated in or was subject to an election.
-
D.
firstElectionUnder
Indicates that an election was the first one conducted under a particular rule, system, constitution, or governing framework.
-
E.
firstElectionAfter
Indicates that one election is the earliest election that occurs after another specified election.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e34e1ee0819092f679d916e6e532 |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.