Triple
T26170634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berserker Kill |
E654390
|
entity |
| Predicate | hasMainOpposingForce |
P68850
|
FINISHED |
| Object | Berserker fleet |
—
|
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 fleet | Statement: [Berserker Kill, hasMainOpposingForce, Berserker fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainOpposingForce Context triple: [Berserker Kill, hasMainOpposingForce, Berserker fleet]
-
A.
hasOpposingForceType
Indicates that one force is characterized as being of a type that opposes or counteracts another force.
-
B.
hasOpposingFront
Indicates that one entity’s front side is directly facing or oriented opposite to the front side of another entity.
-
C.
primaryOpposingForceSize
Indicates the size or magnitude of the main opposing force acting against a subject in a given context.
-
D.
hasMainAdversary
chosen
Indicates that an entity’s primary or most significant opponent, rival, or enemy is another specified entity.
-
E.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
- 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_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 26, 2026, 8:35 p.m.