Triple
T28673332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jakob Grayson |
E725788
|
entity |
| Predicate | universeSetting |
P115007
|
FINISHED |
| Object | world ravaged by a deadly spore |
—
|
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: world ravaged by a deadly spore | Statement: [Jakob Grayson, universeSetting, world ravaged by a deadly spore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: universeSetting Context triple: [Jakob Grayson, universeSetting, world ravaged by a deadly spore]
-
A.
settingInUniverse
chosen
Indicates that one entity is set or takes place within the fictional universe defined by another entity.
-
B.
cosmicSetting
Indicates that an entity is set or takes place within a cosmic, outer-space, or universe-scale environment or context.
-
C.
universeName
Indicates the name or designated title assigned to a particular universe or cosmic setting.
-
D.
universe
Indicates that something pertains to, exists within, or is associated with the entirety of space, time, matter, and phenomena collectively referred to as the universe.
-
E.
universeNumber
Indicates that an entity is associated with a specific universe identified by a particular number or index.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:05 a.m.