Triple
T34370835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le maschere |
E882147
|
entity |
| Predicate | firstPerformedSimultaneouslyIn |
P205413
|
FINISHED |
| Object | Milan |
E11464
|
NE 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: Milan | Statement: [Le maschere, firstPerformedSimultaneouslyIn, Milan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformedSimultaneouslyIn Context triple: [Le maschere, firstPerformedSimultaneouslyIn, Milan]
-
A.
firstPerformedWith
Indicates that an action or work was initially performed in conjunction with a specified collaborator, group, or medium.
-
B.
releasedSimultaneouslyWith
Indicates that two or more entities were made available or launched at the same time or on the same date.
-
C.
firstPerformedDuring
Indicates that an action, event, or performance occurred for the first time within a specified time period or during a particular event.
-
D.
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.
-
E.
firstPerformedAs
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.
- F. None of above. chosen
Provenance (5 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a370db872808190851fb85c2c253bc9 |
completed | June 20, 2026, 10:01 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:59 a.m.