Triple
T29142452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amethyst, Princess of Gemworld |
E738672
|
entity |
| Predicate | magicSystemBasedOn |
P121686
|
FINISHED |
| Object | gemstones |
—
|
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: gemstones | Statement: [Amethyst, Princess of Gemworld, magicSystemBasedOn, gemstones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magicSystemBasedOn Context triple: [Amethyst, Princess of Gemworld, magicSystemBasedOn, gemstones]
-
A.
magicField
Indicates the presence or influence of a magical force or energy affecting an entity or area.
-
B.
usesMagicFor
Indicates that one entity employs or applies magic as a means to achieve, affect, or perform something involving another entity or context.
-
C.
featuresMagicSystem
chosen
Indicates that a work includes or is built around a defined system of magic or supernatural powers.
-
D.
usesMagic
Indicates that an entity performs actions or achieves effects by employing magical powers or supernatural abilities.
-
E.
magicalObjectThatControls
Indicates a relationship where one magical object has the power to direct, influence, or command another entity or force.
- 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_69f07cb3adb48190a9e0e169cd026634 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 11:37 a.m.