Triple
T26070517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berserker Wars |
E657529
|
entity |
| Predicate | workInAuthorUniverse |
P102057
|
FINISHED |
| Object | Berserker universe |
—
|
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: Berserker universe | Statement: [Berserker Wars, workInAuthorUniverse, Berserker universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workInAuthorUniverse Context triple: [Berserker Wars, workInAuthorUniverse, Berserker universe]
-
A.
workAuthoredInUniverse
chosen
Indicates that a creative work is set within, or narratively belongs to, a particular fictional or conceptual universe.
-
B.
workInAuthorSeries
Indicates that a work is part of an author-defined series or collection.
-
C.
fictionalUniverseAuthor
Indicates that an author is the creator or primary writer responsible for a given fictional universe.
-
D.
fictionalUniverseOwner
Indicates that one entity is the creator, rights holder, or controlling owner of a particular fictional universe or setting.
-
E.
workInFiction
Indicates that one entity is a fictional work in which the other entity appears or is set.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606ca69b08190977693fd1f8e8ae4 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 7:28 p.m.