Triple
T38656924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeff Anderson |
E939915
|
entity |
| Predicate | hasWorkInUniverse |
P102057
|
FINISHED |
| Object | View Askewniverse |
—
|
NE NERFINISHED |
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: View Askewniverse | Statement: [Jeff Anderson, hasWorkInUniverse, View Askewniverse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkInUniverse Context triple: [Jeff Anderson, hasWorkInUniverse, View Askewniverse]
-
A.
sameUniverseWorkAs
Indicates that two works are set within the same fictional universe or continuity.
-
B.
hasInUniverseActivity
Indicates that an entity participates in or is associated with a specific activity within a particular fictional or defined universe.
-
C.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
D.
hasWorkOn
Indicates that one entity is associated with, contributes to, or performs work on another entity (such as a project, task, or artifact).
-
E.
workAuthoredInUniverse
chosen
Indicates that a creative work is set within, or narratively belongs to, a particular fictional or conceptual universe.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: May 3, 2026, 4:33 p.m.