Triple
T18261056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muggle |
E437353
|
entity |
| Predicate | perceivedByWizardsAs |
P131073
|
FINISHED |
| Object | technologically advanced but non-magical |
—
|
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: technologically advanced but non-magical | Statement: [Muggle, perceivedByWizardsAs, technologically advanced but non-magical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perceivedByWizardsAs Context triple: [Muggle, perceivedByWizardsAs, technologically advanced but non-magical]
-
A.
typeOfMagic
Indicates that one entity is a specific category, school, or kind of magic associated with another entity.
-
B.
attitudeTowardMagic
Indicates an entity’s stance, feelings, or disposition toward the use or existence of magic.
-
C.
hasSupernaturalPerceptionOf
Indicates that one entity possesses a supernatural or extrasensory awareness, insight, or perception specifically directed toward another entity.
-
D.
enchantedBy
Indicates that one entity has cast or holds a magical enchantment over another entity.
-
E.
enchantedAs
Indicates that one entity has been placed under a magical spell or charm by another entity or force.
- F. None of above. chosen
Provenance (4 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff7591b4819083f2b29d60298747 |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:34 a.m.