Triple
T20192155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nightmare |
E493000
|
entity |
| Predicate | bossForm |
P98692
|
FINISHED |
| Object | Nightmare Power Orb |
—
|
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: Nightmare Power Orb | Statement: [Nightmare, bossForm, Nightmare Power Orb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bossForm Context triple: [Nightmare, bossForm, Nightmare Power Orb]
-
A.
daemonForms
Indicates that one entity takes the form of, manifests as, or is represented by a daemon associated with another entity.
-
B.
bossFeature
Indicates that one entity serves as a primary or dominant feature, element, or component in relation to another.
-
C.
bossCharacter
chosen
Indicates that one character serves as the primary, often more powerful, opponent or leader that others must confront or overcome.
-
D.
daemonForm
Indicates that an entity takes the form, shape, or manifestation of a daemon or demonic being.
-
E.
backForm
Indicates that an entity serves as a reverse, supporting, or rear-facing structure or configuration relative to another entity or form.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad654648190a27521e6e8ea40c5 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.