Triple
T17518537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caldari State |
E426626
|
entity |
| Predicate | notableWeaponSpecialization |
P22495
|
FINISHED |
| Object | kinetic missiles |
—
|
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: kinetic missiles | Statement: [Caldari State, notableWeaponSpecialization, kinetic missiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWeaponSpecialization Context triple: [Caldari State, notableWeaponSpecialization, kinetic missiles]
-
A.
weaponDiscipline
chosen
Indicates that an entity practices, adheres to, or is governed by a particular system, style, or code of weapon use or combat training.
-
B.
specialWeapon
Indicates that an entity is a weapon with unique, enhanced, or otherwise exceptional properties compared to standard weapons.
-
C.
weaponForgedFor
Indicates that a weapon was specifically created or crafted for a particular entity, purpose, or context.
-
D.
craftSpecialty
Indicates that an entity has a particular area of specialized skill or focus within a craft or artisanal practice.
-
E.
dedicatedToWeapon
Indicates that something is specifically assigned, reserved, or purposed for use with a particular weapon or type of weapon.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d0daa48190be69aff32b0324bc |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.