Triple
T33631486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurovision Song Contest 1973 |
E861573
|
entity |
| Predicate | hostedByCountryConsecutively |
P180283
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eurovision Song Contest 1973, hostedByCountryConsecutively, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedByCountryConsecutively Context triple: [Eurovision Song Contest 1973, hostedByCountryConsecutively, true]
-
A.
hostedByCountry
Indicates that an event or activity is organized, held, or officially hosted within the jurisdiction of a specific country.
-
B.
numberOfOpenChampionshipsHosted
Indicates the count of Open Championship golf tournaments that have been hosted by a given entity.
-
C.
runnerUpConsecutiveAppearances
Indicates that an entity has achieved runner-up status in a competition for a specified number of consecutive appearances or editions.
-
D.
secondTimeHostedInContinent
Indicates that an event is being hosted in a given continent for the second time.
-
E.
hostCityStreak
Indicates a sequence or run of consecutive times a particular city has served as the host for a recurring event.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
| PDg | Predicate description generation | batch_69f739a58b3c81908abc2b8738a65678 |
completed | May 3, 2026, 12:03 p.m. |
Created at: May 1, 2026, 1:41 a.m.