Triple
T37459473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troggzor the Earthinator |
E930881
|
entity |
| Predicate | summonsOn |
P119734
|
FINISHED |
| Object | opponent spell cast |
—
|
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: opponent spell cast | Statement: [Troggzor the Earthinator, summonsOn, opponent spell cast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summonsOn Context triple: [Troggzor the Earthinator, summonsOn, opponent spell cast]
-
A.
summoned
Indicates that one entity has called forth, invoked, or ordered the appearance of another entity, typically through authority, command, or supernatural means.
-
B.
summonedAt
Indicates the time or place at which an entity is called, invoked, or brought into presence, typically by another agent or process.
-
C.
convenesOnRequestOf
Indicates that one entity is brought together or assembled at the initiative or formal request of another entity.
-
D.
summonedIn
chosen
Indicates that one entity is called forth, invoked, or brought into presence within the context, location, or event represented by another entity.
-
E.
summonCount
Indicates the number of times an entity has been summoned or caused to appear.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:17 p.m.