Triple
T17746732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hellmouth |
E443007
|
entity |
| Predicate | canBeSealedBy |
P58658
|
FINISHED |
| Object | powerful magic |
—
|
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: powerful magic | Statement: [Hellmouth, canBeSealedBy, powerful magic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeSealedBy Context triple: [Hellmouth, canBeSealedBy, powerful magic]
-
A.
isSealed
Indicates that an entity is closed off or secured so that nothing can enter, exit, or be altered.
-
B.
canBeSeizedBy
Indicates that one entity is legally or physically able to be taken control of, captured, or confiscated by another entity.
-
C.
canBeLocked
Indicates that an entity has the capability to be secured or made inaccessible by applying a lock or locking mechanism.
-
D.
sealedBy
chosen
Indicates that one entity is closed, secured, or made airtight/watertight through the action or presence of another entity.
-
E.
canBeSecret
Indicates that something has the potential or suitability to be kept hidden or confidential from others.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47ad26940819090696c2cb86fd606 |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:09 a.m.