Triple
T10109172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirov-class battlecruiser |
E218196
|
entity |
| Predicate | primaryAntiShipMissileType |
P75754
|
FINISHED |
| Object | long-range supersonic cruise missile |
—
|
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: long-range supersonic cruise missile | Statement: [Kirov-class battlecruiser, primaryAntiShipMissileType, long-range supersonic cruise missile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAntiShipMissileType Context triple: [Kirov-class battlecruiser, primaryAntiShipMissileType, long-range supersonic cruise missile]
-
A.
missileClass
Indicates the classification or type category assigned to a missile within a defined system or taxonomy.
-
B.
missileTypeCarried
chosen
Indicates the specific type or category of missile that is carried by a given platform, launcher, or delivery system.
-
C.
numberOfMissileTubes
Indicates the quantity of missile tubes that an entity possesses or is equipped with.
-
D.
missileLaunchCapability
Indicates that an entity has the ability or functionality to launch missiles.
-
E.
missileTubesPerBoat
Indicates the number of missile tubes associated with each individual boat in the relationship.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd0cbd8a48190b2af6177d1249f58 |
completed | April 2, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:03 p.m.