Triple
T28704454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarre |
E729649
|
entity |
| Predicate | hadPlebisciteIn |
P32657
|
FINISHED |
| Object | 1935 |
—
|
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: 1935 | Statement: [Sarre, hadPlebisciteIn, 1935]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPlebisciteIn Context triple: [Sarre, hadPlebisciteIn, 1935]
-
A.
referendumHeldAmong
Indicates that a referendum was conducted among a specified group or population as the decision-making body.
-
B.
plebisciteHeldInYear
chosen
Indicates that a plebiscite (a direct vote by the electorate on a specific issue) was held in the specified year.
-
C.
heldReferendum
Indicates that an entity organized and conducted a referendum, typically allowing eligible participants to vote directly on a specific issue or proposal.
-
D.
referendumResult
Indicates the outcome or decision reached by voters in a specific referendum.
-
E.
referendumEvent
Indicates that an event is a referendum, i.e., a formal process in which eligible participants vote directly to accept or reject a specific proposal or decision.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f656b6d94c8190ab3d7530603f53e9 |
completed | May 2, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:44 a.m.