Triple
T19918193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoo City |
E478718
|
entity |
| Predicate | setInAlternateReality |
P18263
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zoo City, setInAlternateReality, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInAlternateReality Context triple: [Zoo City, setInAlternateReality, true]
-
A.
hasAlternateTimeline
Indicates that an entity exists or occurs in a different possible or parallel timeline relative to another reference timeline.
-
B.
setInFictionalLocation
chosen
Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
-
C.
alternateUniverseVersionOf
Indicates that one entity is a counterpart or variant of another entity existing in a different universe or reality.
-
D.
alternateTimelineName
Indicates that one entity is the name or designation used for another entity in an alternate or parallel timeline.
-
E.
setInUniverseDuring
Indicates that an event, story, or situation takes place within a particular universe during a specified time or period.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c3d990819089386d9f30323e8c |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.