Triple
T33631467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurovision Song Contest 1973 |
E861573
|
entity |
| Predicate | votingDetails |
P76673
|
FINISHED |
| Object | each country had two jurors aged 16–25 and 26–55 |
—
|
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: each country had two jurors aged 16–25 and 26–55 | Statement: [Eurovision Song Contest 1973, votingDetails, each country had two jurors aged 16–25 and 26–55]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingDetails Context triple: [Eurovision Song Contest 1973, votingDetails, each country had two jurors aged 16–25 and 26–55]
-
A.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated in a voting process.
-
B.
electionDetail
chosen
Indicates that additional specific information or attributes are being provided about a particular election.
-
C.
votingResultNoPercentage
Indicates that a voting outcome is recorded or reported without specifying the percentage of votes for each option.
-
D.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
E.
voteResult
Indicates the outcome or decision produced by a voting process involving the related entities.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:41 a.m.