Triple
T23218207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HWV 34 |
E580807
|
entity |
| Predicate | hasDisguiseMotif |
P20150
|
FINISHED |
| Object | Bradamante disguised as Ricciardo |
—
|
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: Bradamante disguised as Ricciardo | Statement: [HWV 34, hasDisguiseMotif, Bradamante disguised as Ricciardo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisguiseMotif Context triple: [HWV 34, hasDisguiseMotif, Bradamante disguised as Ricciardo]
-
A.
usesMasksOrDisguises
Indicates that an entity employs masks, costumes, or other forms of disguise to conceal or alter its identity in the context of an action or interaction.
-
B.
disguisedAs
chosen
Indicates that one entity is intentionally presenting itself as, or made to appear as, another entity in order to conceal its true identity.
-
C.
reasonForDisguise
Indicates the motive or purpose behind an entity adopting a disguise.
-
D.
isCostumed
Indicates that an entity is wearing or otherwise adorned with a costume.
-
E.
hasMascotIdentity
Indicates that an entity serves as or possesses the role/identity of a mascot for 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1916653f08190a7dcbc659c6b6a25 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.