Triple
T32073468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Force de frappe |
E819077
|
entity |
| Predicate | formerAirLaunchedMissile |
P199876
|
FINISHED |
| Object | ASMP |
—
|
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: ASMP | Statement: [Force de frappe, formerAirLaunchedMissile, ASMP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerAirLaunchedMissile Context triple: [Force de frappe, formerAirLaunchedMissile, ASMP]
-
A.
notableMissile
Indicates that the subject is a missile distinguished by particular significance, prominence, or noteworthiness (e.g., historical impact, technological importance, or public attention).
-
B.
missileClass
Indicates the classification or type category assigned to a missile within a defined system or taxonomy.
-
C.
missileLaunchCapability
Indicates that an entity has the ability or functionality to launch missiles.
-
D.
missileTypeCarried
Indicates the specific type or category of missile that is carried by a given platform, launcher, or delivery system.
-
E.
missileFamily
Indicates that one missile belongs to, or is categorized within, the same family or series as another missile.
- F. None of above. chosen
Provenance (4 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
| PDg | Predicate description generation | batch_69ff607407a881909d9e6e1c98559a6e |
completed | May 9, 2026, 4:27 p.m. |
Created at: May 1, 2026, 12:23 a.m.