Triple
T28941925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank the Thunderbird |
E730473
|
entity |
| Predicate | magicalProperty |
P62729
|
FINISHED |
| Object | weather manipulation |
—
|
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: weather manipulation | Statement: [Frank the Thunderbird, magicalProperty, weather manipulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magicalProperty Context triple: [Frank the Thunderbird, magicalProperty, weather manipulation]
-
A.
magicalObject
Indicates that one entity is a magical object associated with, used by, or affecting another entity.
-
B.
magicField
Indicates the presence or influence of a magical force or energy affecting an entity or area.
-
C.
magicalStatus
chosen
Indicates that an entity possesses, is affected by, or is characterized in terms of a particular magical condition or property.
-
D.
magicalObjectThatControls
Indicates a relationship where one magical object has the power to direct, influence, or command another entity or force.
-
E.
usesMagicFor
Indicates that one entity employs or applies magic as a means to achieve, affect, or perform something involving another entity or context.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 8:37 a.m.