Triple
T26170341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berserkers |
E654382
|
entity |
| Predicate | programmedPurpose |
P162319
|
FINISHED |
| Object | destroy biological intelligence |
—
|
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: destroy biological intelligence | Statement: [Berserkers, programmedPurpose, destroy biological intelligence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmedPurpose Context triple: [Berserkers, programmedPurpose, destroy biological intelligence]
-
A.
intendedProgram
Indicates the academic or training program that an entity plans or expects to pursue, rather than one they are currently enrolled in or have completed.
-
B.
programmedVia
Indicates that one entity is created, configured, or made to operate through the use of another entity as its programming method, tool, or medium.
-
C.
traditionalPurpose
Indicates that something serves a role, function, or use that is established by long-standing custom or tradition.
-
D.
usedAsProgramFor
Indicates that one entity functions as the software or application used to operate, control, or provide services for another entity.
-
E.
scriptPurpose
Indicates the intended function or role that a script is designed to perform.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6250321088190ae3ed1dc9f2fcd03 |
completed | May 2, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f62473a38481909b919f88ffb5b492 |
completed | May 2, 2026, 4:21 p.m. |
Created at: April 26, 2026, 8:34 p.m.