Triple
T20473251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | secret passage to Hogwarts |
E502247
|
entity |
| Predicate | accessSpell |
P138209
|
FINISHED |
| Object | Dissendium |
—
|
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: Dissendium | Statement: [secret passage to Hogwarts, accessSpell, Dissendium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessSpell Context triple: [secret passage to Hogwarts, accessSpell, Dissendium]
-
A.
accessedBySpell
chosen
Indicates that something is reached, activated, or utilized through the use of a spell.
-
B.
underSpellBy
Indicates that one entity is magically influenced, controlled, or enchanted by another entity.
-
C.
usedSpell
Indicates that one entity has cast or employed a particular spell on or in relation to another entity or context.
-
D.
spells
Indicates that one entity writes or names the letters of a word or sequence in their correct order for another entity or context.
-
E.
usedForSpell
Indicates that something serves as a component, tool, or resource employed in performing or casting a spell.
- 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69962d810819091bb13fe73250e24 |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.