Triple
T16822885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GBU-27 Paveway III |
E408938
|
entity |
| Predicate | guidanceKitGeneration |
P124137
|
FINISHED |
| Object | third generation Paveway |
—
|
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: third generation Paveway | Statement: [GBU-27 Paveway III, guidanceKitGeneration, third generation Paveway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidanceKitGeneration Context triple: [GBU-27 Paveway III, guidanceKitGeneration, third generation Paveway]
-
A.
usesGuidanceKit
Indicates that one entity employs or relies on a guidance kit to direct, control, or navigate another entity or process.
-
B.
guidanceIntegration
Indicates how one entity incorporates, applies, or aligns with the advice, instructions, or direction provided by another entity.
-
C.
guidanceKitFamily
chosen
Indicates a relationship where one entity belongs to, or is categorized within, a particular family or group of guidance kits.
-
D.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
E.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e838e881908b650194c9b94886 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.