Triple
T23071246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intermediate-range ballistic missile |
E575200
|
entity |
| Predicate | capableOfCarrying |
P98937
|
FINISHED |
| Object | Conventional warhead |
—
|
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: Conventional warhead | Statement: [Intermediate-range ballistic missile, capableOfCarrying, Conventional warhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capableOfCarrying Context triple: [Intermediate-range ballistic missile, capableOfCarrying, Conventional warhead]
-
A.
canBeBorneBy
chosen
Indicates that one entity is capable of being carried, supported, or transported by another entity.
-
B.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
-
C.
slingLoadCapacity
Indicates the maximum weight or load that can be safely carried or supported using a sling.
-
D.
cargoCapacityFeature
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
-
E.
cargoCapacityConfigurable
Indicates that the cargo capacity of an entity can be adjusted or configured rather than being fixed.
- 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18c5ffad881909ed626045c15dd33 |
completed | April 29, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:56 p.m.