Triple
T20210268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patronus Charm |
E493469
|
entity |
| Predicate | requiresWandMovement |
P139205
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Patronus Charm, requiresWandMovement, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresWandMovement Context triple: [Patronus Charm, requiresWandMovement, yes]
-
A.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
-
B.
usesMove
Indicates that an entity performs or executes a specific move or action.
-
C.
requiresPlayerActionToSpawn
Indicates that the entity or event will only appear or be created when a player performs a specific action.
-
D.
movementDemand
Indicates a requirement or request for an entity to move or be moved from one location or state to another.
-
E.
requiresControlInput
Indicates that an entity cannot function or proceed autonomously and instead depends on receiving control commands or input from another agent or system.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed4706c81908a5e4a3023a9c22f |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:38 p.m.