Triple
T34643443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ally Andrews |
E889631
|
entity |
| Predicate | worldSetting |
P40428
|
FINISHED |
| Object | post-apocalyptic world overrun by sound-hunting creatures |
—
|
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: post-apocalyptic world overrun by sound-hunting creatures | Statement: [Ally Andrews, worldSetting, post-apocalyptic world overrun by sound-hunting creatures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldSetting Context triple: [Ally Andrews, worldSetting, post-apocalyptic world overrun by sound-hunting creatures]
-
A.
worldType
chosen
Indicates the classification or category of world or environment that an entity is associated with.
-
B.
worldName
Indicates that an entity has or is associated with a specific world’s name.
-
C.
worldStyle
Indicates the stylistic or aesthetic manner in which a world, setting, or environment is presented or designed.
-
D.
worldbuildingFunction
Indicates the role or purpose something serves in constructing, shaping, or enriching an imagined world or setting.
-
E.
worldEncountered
Indicates that an entity has come into contact with, discovered, or experienced a particular world or environment.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: May 1, 2026, 2:04 a.m.