Triple
T26170471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berserker |
E654385
|
entity |
| Predicate | machineOrigin |
P160003
|
FINISHED |
| Object | ancient interstellar war |
—
|
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: ancient interstellar war | Statement: [Berserker, machineOrigin, ancient interstellar war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: machineOrigin Context triple: [Berserker, machineOrigin, ancient interstellar war]
-
A.
originallyBuiltBy
Indicates that something was first constructed or created by a particular agent, organization, or entity.
-
B.
engineOriginCountry
Indicates the country where an engine was originally designed, manufactured, or first produced.
-
C.
physicalOrigin
Indicates that one entity is the place or source from which another entity physically originates or comes into existence.
-
D.
chassisOrigin
Indicates the place or source from which a chassis was originally produced, manufactured, or derived.
-
E.
originOfEngine
Indicates the source or place from which an engine originates or is produced.
- 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_69f60c425de88190a221b40e81d0dcc1 |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:35 p.m.