Triple
T25193931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andre Anthony |
E630951
|
entity |
| Predicate | settingUniverseType |
P16450
|
FINISHED |
| Object | post-apocalyptic zombie outbreak |
—
|
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 zombie outbreak | Statement: [Andre Anthony, settingUniverseType, post-apocalyptic zombie outbreak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingUniverseType Context triple: [Andre Anthony, settingUniverseType, post-apocalyptic zombie outbreak]
-
A.
settingInUniverse
Indicates that one entity is set or takes place within the fictional universe defined by another entity.
-
B.
setInUniverse
chosen
Indicates that something is located within, belongs to, or takes place in a particular fictional or conceptual universe.
-
C.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
D.
universeName
Indicates the name or designated title assigned to a particular universe or cosmic setting.
-
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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 12:45 p.m.