Triple
T28298999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volare |
E713651
|
entity |
| Predicate | wasPerformedAt |
P164248
|
FINISHED |
| Object | Eurovision Song Contest 1958 |
—
|
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: Eurovision Song Contest 1958 | Statement: [Volare, wasPerformedAt, Eurovision Song Contest 1958]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPerformedAt Context triple: [Volare, wasPerformedAt, Eurovision Song Contest 1958]
-
A.
performedWhen
Indicates the specific time or temporal condition under which an action or event was carried out.
-
B.
takenOn
Indicates that something (such as a photo, measurement, or record) was captured or recorded at a specific time or on a specific date.
-
C.
conductedOn
Indicates that an action, process, or event was carried out with respect to, or took place on, a specified subject, object, or medium.
-
D.
performedFrom
Indicates that an action or operation is carried out starting at or originating from a specified source location, context, or entity.
-
E.
firstPerformedDuring
Indicates that an action, event, or performance occurred for the first time within a specified time period or during a particular 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f644b13498819095df64be37e48ae0 |
completed | May 2, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 27, 2026, 11:34 p.m.