Triple
T16021845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GBU-51 JDAM |
E388618
|
entity |
| Predicate | hasMassClass |
P100393
|
FINISHED |
| Object | 500 lb |
—
|
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: 500 lb | Statement: [GBU-51 JDAM, hasMassClass, 500 lb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMassClass Context triple: [GBU-51 JDAM, hasMassClass, 500 lb]
-
A.
hasMassBaseAmong
Indicates that one entity possesses a fundamental or baseline mass value when considered among a specified group or context.
-
B.
hasMassScale
Indicates that an entity is associated with a particular mass measurement scale or system used to quantify its mass.
-
C.
hasMasses
chosen
Indicates that one entity possesses or is associated with one or more masses (quantities of matter).
-
D.
hasMassTerm
Indicates that one entity is classified as a mass (uncountable) term associated with another entity.
-
E.
isMassive
Indicates that one entity has an extremely large size, scale, or extent relative to typical or comparable entities.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:55 a.m.