Triple
T14566942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaos Walking |
E341807
|
entity |
| Predicate | fictionalConcept |
P81118
|
FINISHED |
| Object | Noise |
—
|
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: Noise | Statement: [Chaos Walking, fictionalConcept, Noise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalConcept Context triple: [Chaos Walking, fictionalConcept, Noise]
-
A.
fictionalObject
Indicates that one entity is a fictional or imaginary object in relation to another entity.
-
B.
fictionalEntityType
chosen
Indicates that the subject is classified as a particular type or category of fictional entity within a narrative or imaginary context.
-
C.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by another entity.
-
D.
fictionalTheme
Indicates that a work, element, or context is centered around or characterized by a fictional theme or motif.
-
E.
fictionalCharacter
Indicates that one entity is a fictional character that appears within the narrative world of another entity (such as a work, series, or franchise).
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb38d89fc819086709fd3607b835f |
completed | April 14, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.