Triple
T28298994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volare |
E713651
|
entity |
| Predicate | wasFirstPerformedBy |
P66089
|
FINISHED |
| Object | Domenico Modugno |
—
|
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: Domenico Modugno | Statement: [Volare, wasFirstPerformedBy, Domenico Modugno]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFirstPerformedBy Context triple: [Volare, wasFirstPerformedBy, Domenico Modugno]
-
A.
firstPerformedAs
chosen
Indicates the initial occasion or context in which an entity (such as a work, role, or piece) was performed by a particular performer or group.
-
B.
firstPerformedAsPartOf
Indicates that an action or performance first occurred within the context of, or as a component of, a specific larger event, work, or production.
-
C.
firstPerformedWith
Indicates that an action or work was initially performed in conjunction with a specified collaborator, group, or medium.
-
D.
wasFirst
Indicates that one entity occurred, appeared, or held a position before another in time or sequence.
-
E.
firstPerformedOn
Indicates the date or occasion on which an action, event, or performance was carried out for the first time on a particular subject or object.
- 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_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. |
Created at: April 27, 2026, 11:34 p.m.