Triple
T26170708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berserker Prime |
E654392
|
entity |
| Predicate | hasFictionalConflict |
P176713
|
FINISHED |
| Object | humans vs Berserkers |
—
|
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: humans vs Berserkers | Statement: [Berserker Prime, hasFictionalConflict, humans vs Berserkers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalConflict Context triple: [Berserker Prime, hasFictionalConflict, humans vs Berserkers]
-
A.
hasFictionalUniverseConflict
Indicates that there is a conflict or incompatibility between the fictional universes associated with the related entities.
-
B.
fictionalConflict
chosen
Indicates a relationship where one fictional entity is in opposition, dispute, or struggle with another within a narrative context.
-
C.
hasFictionalWar
Indicates that there exists a fictional or imagined war involving the related entities.
-
D.
hasFictionalContent
Indicates that something contains or includes material that is imaginary, invented, or not intended to represent real events or facts.
-
E.
hasFictionalFrame
Indicates that one entity is presented or interpreted within the context of a fictional narrative, scenario, or imaginative framework provided by another entity.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 26, 2026, 8:35 p.m.