Triple
T23680653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Calisto |
E585007
|
entity |
| Predicate | featuresRoleType |
P5518
|
FINISHED |
| Object | trouser role of Giove disguised as Diana |
—
|
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: trouser role of Giove disguised as Diana | Statement: [La Calisto, featuresRoleType, trouser role of Giove disguised as Diana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresRoleType Context triple: [La Calisto, featuresRoleType, trouser role of Giove disguised as Diana]
-
A.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
B.
typeOfRole
chosen
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
C.
profileRole
Indicates the specific role or function an entity holds within a given profile or contextual configuration.
-
D.
formRole
Indicates that an entity assumes, is assigned, or functions in a particular role within a specified context or structure.
-
E.
identificationRole
Indicates that an entity serves as an identifier or plays a role in uniquely distinguishing or recognizing another entity.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f835ec8190a7bdcfa48ad79cd5 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.