Triple
T26070487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berserker Death |
E657528
|
entity |
| Predicate | literarySeriesSubject |
P165840
|
FINISHED |
| Object | Berserker–human conflict |
—
|
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: Berserker–human conflict | Statement: [Berserker Death, literarySeriesSubject, Berserker–human conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literarySeriesSubject Context triple: [Berserker Death, literarySeriesSubject, Berserker–human conflict]
-
A.
literarySeriesGenre
Indicates that a literary series belongs to or is categorized under a particular genre.
-
B.
literarySeries
Indicates that one work is part of, or belongs to, a larger literary series that connects multiple related works.
-
C.
literarySeriesType
Indicates the specific kind or category of a literary series that an entity belongs to or is characterized as.
-
D.
literarySeriesPublisher
Indicates the publishing company responsible for producing or releasing a given literary series.
-
E.
literarySubject
Indicates that one entity serves as the subject, topic, or focus of a literary work created by another entity.
- F. None of above. chosen
Provenance (4 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_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a9cb0bc8190bf8a9b319900bad5 |
completed | May 2, 2026, 8:12 p.m. |
Created at: April 26, 2026, 7:28 p.m.