Triple
T37059656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Il pirata |
E917287
|
entity |
| Predicate | originalCastRole |
P151606
|
FINISHED |
| Object | Gualtiero |
E208903
|
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: Gualtiero | Statement: [Il pirata, originalCastRole, Gualtiero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCastRole Context triple: [Il pirata, originalCastRole, Gualtiero]
-
A.
originalCast
Indicates that the subject is a member of the initial group of performers or participants who first originated a role or production.
-
B.
originalCastPerformer
Indicates that a performer was part of the original cast in the first production or release of a work.
-
C.
mainCastMemberRole
Indicates that an entity’s role specifies the character or position they portray as a principal member of a production’s main cast.
-
D.
originalLeadActorRole
chosen
Indicates the role originally played by a particular lead actor in a given production or work.
-
E.
originalReleaseRole
Indicates the specific role an entity played in the original release of a work, such as how it contributed or participated in that initial publication or distribution.
- F. None of above.
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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40511496708190801a4ed01bf129b3 |
completed | June 27, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.