Triple
T18763980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi F-1 |
E458845
|
entity |
| Predicate | primaryArmamentRole |
P84541
|
FINISHED |
| Object | anti-ship missiles |
—
|
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: anti-ship missiles | Statement: [Mitsubishi F-1, primaryArmamentRole, anti-ship missiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryArmamentRole Context triple: [Mitsubishi F-1, primaryArmamentRole, anti-ship missiles]
-
A.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
B.
refersToArmamentRole
chosen
Indicates that one entity specifies or denotes the armament-related role or function associated with another entity.
-
C.
primaryArms
Indicates that the subject possesses or uses the specified arms or weapons as its main or most important set.
-
D.
primaryArmamentLayout
Indicates how the main weapons or primary armament of an entity are arranged or distributed relative to that entity.
-
E.
secondaryArmament
Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d82297c81909f720e2637cec737 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.