Triple
T29842310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilda |
E757832
|
entity |
| Predicate | protectiveFigure |
P148313
|
FINISHED |
| Object | Rigoletto |
—
|
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: Rigoletto | Statement: [Gilda, protectiveFigure, Rigoletto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectiveFigure Context triple: [Gilda, protectiveFigure, Rigoletto]
-
A.
shieldDepicts
Indicates that a shield bears or displays a particular image, symbol, or design as its depiction.
-
B.
protectingPowerFor
Indicates that one entity serves as a protecting power, safeguarding the interests or rights of another entity, typically in a diplomatic or conflict-related context.
-
C.
protectors
chosen
Indicates a relationship where one entity actively safeguards, defends, or shields another from harm, danger, or adverse effects.
-
D.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
E.
aimsToProtect
Indicates an intention or purpose to safeguard or defend one entity, value, or condition from harm, risk, or undesirable outcomes.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 5:40 p.m.