Triple
T28639058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quaffle |
E724868
|
entity |
| Predicate | isNonMagicalObjectWith |
P166887
|
FINISHED |
| Object | magical enhancements |
—
|
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: magical enhancements | Statement: [Quaffle, isNonMagicalObjectWith, magical enhancements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonMagicalObjectWith Context triple: [Quaffle, isNonMagicalObjectWith, magical enhancements]
-
A.
magicalObject
Indicates that one entity is a magical object associated with, used by, or affecting another entity.
-
B.
magicalObjectThatControls
Indicates a relationship where one magical object has the power to direct, influence, or command another entity or force.
-
C.
usesMagicFor
Indicates that one entity employs or applies magic as a means to achieve, affect, or perform something involving another entity or context.
-
D.
hasMagicItem
Indicates that an entity possesses or is associated with a magical item.
-
E.
associatedWithMagicType
Indicates a relationship where something is linked or connected to a particular type or category of magic.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 4:42 a.m.