Triple
T3481004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taurus KEPD 350 |
E73488
|
entity |
| Predicate | terminalGuidance |
P6753
|
FINISHED |
| Object | imaging infrared seeker with target recognition |
—
|
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: imaging infrared seeker with target recognition | Statement: [Taurus KEPD 350, terminalGuidance, imaging infrared seeker with target recognition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalGuidance Context triple: [Taurus KEPD 350, terminalGuidance, imaging infrared seeker with target recognition]
-
A.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to another entity.
-
B.
guidanceType
chosen
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
C.
guidedBy
Indicates that an entity’s actions, decisions, or movement are directed, advised, or led by another entity.
-
D.
terminusDirection
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
E.
directedTo
Indicates that something is sent, aimed, or addressed toward a particular target or recipient.
- 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_69ad85b3c9b08190857cae74c7f36da9 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb75850c8190ad02cf2bde8be8a7 |
completed | March 8, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69adae0935ac8190bfa8a8bd3dcd3301 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.