Triple
T11152260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barrow-blade |
E263814
|
entity |
| Predicate | enchantment |
P98120
|
FINISHED |
| Object | effective against servants of the Dark Lord |
—
|
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: effective against servants of the Dark Lord | Statement: [Barrow-blade, enchantment, effective against servants of the Dark Lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enchantment Context triple: [Barrow-blade, enchantment, effective against servants of the Dark Lord]
-
A.
enchantedBy
Indicates that one entity has cast or holds a magical enchantment over another entity.
-
B.
typeOfMagic
Indicates that one entity is a specific category, school, or kind of magic associated with another entity.
-
C.
spells
Indicates that one entity writes or names the letters of a word or sequence in their correct order for another entity or context.
-
D.
notableSpell
Indicates that a particular spell is especially significant, famous, or noteworthy in some context.
-
E.
usesMagic
Indicates that an entity performs actions or achieves effects by employing magical powers or supernatural abilities.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8719e74819095413abc6c79296c |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce71944819089eee9b5c9283cbd |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d7706116248190a87440bec3960884 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:28 p.m.