Triple
T34345018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eupen-Malmedy |
E881406
|
entity |
| Predicate | plebisciteSupervisedBy |
P179376
|
FINISHED |
| Object | League of Nations |
—
|
NE NERFINISHED |
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: League of Nations | Statement: [Eupen-Malmedy, plebisciteSupervisedBy, League of Nations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plebisciteSupervisedBy Context triple: [Eupen-Malmedy, plebisciteSupervisedBy, League of Nations]
-
A.
plebisciteHeld
Indicates that a public vote or referendum has been conducted to decide a specific issue or proposal.
-
B.
plebisciteHeldInYear
Indicates that a plebiscite (a direct vote by the electorate on a specific issue) was held in the specified year.
-
C.
referendumHeldAmong
Indicates that a referendum was conducted among a specified group or population as the decision-making body.
-
D.
subjectOfReferendum
Indicates that something is the issue, proposal, or matter being decided upon in a referendum.
-
E.
referendumRelated
Indicates a relationship where something is connected to, associated with, or arising from a referendum process or its outcomes.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720cc1bfc8190a16118e3af8e9316 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71fb0172c81908f23e95ff16b0dec |
completed | May 3, 2026, 10:13 a.m. |
Created at: May 1, 2026, 1:58 a.m.