Triple
T31825680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Avalor |
E812386
|
entity |
| Predicate | hasMagicalArtifact |
P97183
|
FINISHED |
| Object | Scepter of Light |
—
|
NE NERFINISHED |
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: Scepter of Light | Statement: [Kingdom of Avalor, hasMagicalArtifact, Scepter of Light]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagicalArtifact Context triple: [Kingdom of Avalor, hasMagicalArtifact, Scepter of Light]
-
A.
hasMagicItem
chosen
Indicates that an entity possesses or is associated with a magical item.
-
B.
hasAccessToMagic
Indicates that one entity is able to use, interact with, or benefit from magical powers, resources, or abilities associated with another entity or source.
-
C.
hasIconicArtifact
Indicates that an entity possesses or is associated with a distinctive, emblematic artifact that represents its identity, history, or significance.
-
D.
hasMagicCompanion
Indicates that an entity is accompanied by or associated with another entity that serves as its magical companion.
-
E.
hasRitualObject
Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a004fd3caf48190b2ec063a7bf0756b |
completed | May 10, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_6a004f7672dc8190aca91d1ed855bf9a |
completed | May 10, 2026, 9:27 a.m. |
Created at: April 30, 2026, 11:46 p.m.