Triple
T14274121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M142 launcher module |
E353870
|
entity |
| Predicate | guidanceCapability |
P6753
|
FINISHED |
| Object | supports guided rockets |
—
|
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: supports guided rockets | Statement: [M142 launcher module, guidanceCapability, supports guided rockets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidanceCapability Context triple: [M142 launcher module, guidanceCapability, supports guided rockets]
-
A.
guidanceIntegration
Indicates how one entity incorporates, applies, or aligns with the advice, instructions, or direction provided by another entity.
-
B.
guidanceType
chosen
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
C.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to another entity.
-
D.
guidanceLocation
Indicates the place or spatial context where guidance, direction, or instructional support is provided or intended to occur.
-
E.
seekerCapability
Indicates that an entity has the ability or function to detect, track, or locate a target or object.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6582f5308190969f4cfd724d9139 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.