Triple
T25218866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buk-M1 |
E631904
|
entity |
| Predicate | transporterLoaderVehicleDesignation |
P167045
|
FINISHED |
| Object | 9A39M1 |
—
|
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: 9A39M1 | Statement: [Buk-M1, transporterLoaderVehicleDesignation, 9A39M1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transporterLoaderVehicleDesignation Context triple: [Buk-M1, transporterLoaderVehicleDesignation, 9A39M1]
-
A.
launcherVehicleDesignation
Indicates the specific launch vehicle or rocket designation associated with an object or mission.
-
B.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
C.
transportUnit
Indicates a relationship where one entity serves as a means or unit for transporting another entity from one place to another.
-
D.
isPressurizedCargoCarrier
Indicates that the entity functions as a cargo carrier whose internal space is maintained at a controlled pressure.
-
E.
vehicleLoadingMethod
Indicates the method or process by which a vehicle is loaded with goods, passengers, or other cargo.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 21, 2026, 12:59 p.m.