Triple
T22149585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W80 warhead |
E547377
|
entity |
| Predicate | guidanceDependency |
P38982
|
FINISHED |
| Object | relies on host cruise missile guidance |
—
|
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: relies on host cruise missile guidance | Statement: [W80 warhead, guidanceDependency, relies on host cruise missile guidance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidanceDependency Context triple: [W80 warhead, guidanceDependency, relies on host cruise missile guidance]
-
A.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to another entity.
-
B.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
C.
guidanceIntegration
Indicates how one entity incorporates, applies, or aligns with the advice, instructions, or direction provided by another entity.
-
D.
guidedBy
Indicates that an entity’s actions, decisions, or movement are directed, advised, or led by another entity.
-
E.
dependency
chosen
Indicates that one entity relies on, is conditioned by, or cannot function or exist properly without 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f2c0e881909c3488bb5eb5959d |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.