Triple
T37929072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keyblade |
E946163
|
entity |
| Predicate | canSeal |
P10498
|
FINISHED |
| Object | Door to Darkness |
—
|
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: Door to Darkness | Statement: [Keyblade, canSeal, Door to Darkness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSeal Context triple: [Keyblade, canSeal, Door to Darkness]
-
A.
usedSeal
chosen
Indicates that an entity has applied or employed a seal (e.g., for closure, authentication, or protection) on another entity.
-
B.
isSealOf
Indicates that one entity serves as the official seal, emblem, or stamp that authenticates, endorses, or formally represents another entity.
-
C.
isSealed
Indicates that an entity is closed off or secured so that nothing can enter, exit, or be altered.
-
D.
requiresSeal
Indicates that one entity must be sealed or have a seal applied as a necessary condition for another entity’s use, validity, or completion.
-
E.
sealType
Indicates the specific kind or category of seal associated with an entity or connection.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.