Triple
T16652485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GBU-10 Paveway II |
E404639
|
entity |
| Predicate | typicalWeightClass |
P8068
|
FINISHED |
| Object | 907 kg |
—
|
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: 907 kg | Statement: [GBU-10 Paveway II, typicalWeightClass, 907 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWeightClass Context triple: [GBU-10 Paveway II, typicalWeightClass, 907 kg]
-
A.
weightClass
chosen
Indicates the categorical grouping of an entity based on its weight range or mass classification.
-
B.
intendedUserWeightClass
Indicates the weight category or range for which a user is specifically targeted or intended.
-
C.
weightClassAlternativeName
Indicates that one weight class is referred to by an alternative name or label.
-
D.
allowsWeightClasses
Indicates that one entity permits or supports the use of defined weight categories for another entity or within a given context.
-
E.
weightClassBelow
Indicates that one entity belongs to a lower (lighter) weight class than another entity.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bf7ae7c81908b6807acd8f1669b |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.