Triple
T24729600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMAS Hobart (DDG 39) |
E618247
|
entity |
| Predicate | antiShipMissile |
P20224
|
FINISHED |
| Object | Harpoon |
—
|
NE NERFINISHED |
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: Harpoon | Statement: [HMAS Hobart (DDG 39), antiShipMissile, Harpoon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antiShipMissile Context triple: [HMAS Hobart (DDG 39), antiShipMissile, Harpoon]
-
A.
associatedWithMissile
Indicates a relationship in which an entity is connected or linked to a missile, such as through ownership, use, design, deployment, or operational involvement.
-
B.
usesMissileSystem
chosen
Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
-
C.
missileLaunchCapability
Indicates that an entity has the ability or functionality to launch missiles.
-
D.
compatibleMissile
Indicates that a missile can be correctly used with, mounted on, or launched by a given platform or launcher system.
-
E.
notableMissile
Indicates that the subject is a missile distinguished by particular significance, prominence, or noteworthiness (e.g., historical impact, technological importance, or public attention).
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:02 a.m.