Triple
T29284258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clara (The Nutcracker) |
E742464
|
entity |
| Predicate | guardianFigure |
P28704
|
FINISHED |
| Object | Drosselmeyer |
—
|
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: Drosselmeyer | Statement: [Clara (The Nutcracker), guardianFigure, Drosselmeyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardianFigure Context triple: [Clara (The Nutcracker), guardianFigure, Drosselmeyer]
-
A.
guardian
chosen
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
-
B.
hasGuardianFigureType
Indicates the type or role of a guardian figure associated with an entity.
-
C.
starGuardOfChampion
Indicates that one entity serves as the primary or most prominent protector or guardian of a champion.
-
D.
guardianDeitiesOrFigures
Indicates a protective or watchful relationship in which certain deities or figures serve as guardians over specific people, places, objects, or domains.
-
E.
guardianShrineOf
Indicates a relationship where one entity serves as a protective or custodial shrine dedicated to 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 12:56 p.m.