Triple
T37461645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thing from Below |
E930931
|
entity |
| Predicate | summoningSynergy |
P189403
|
FINISHED |
| Object | Totem |
—
|
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: Totem | Statement: [Thing from Below, summoningSynergy, Totem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summoningSynergy Context triple: [Thing from Below, summoningSynergy, Totem]
-
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.
summonedIn
Indicates that one entity is called forth, invoked, or brought into presence within the context, location, or event represented by another entity.
-
C.
summoningSound
Indicates a sound produced or used with the purpose of calling, invoking, or bringing forth someone or something.
-
D.
summonedAt
Indicates the time or place at which an entity is called, invoked, or brought into presence, typically by another agent or process.
-
E.
synergyCondition
chosen
Indicates that a specific set of conditions must be met for multiple entities or actions to interact in a mutually enhancing or combined-effect manner.
- 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_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 3, 2026, 4:17 p.m.