Triple
T18650141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIM-54 Phoenix |
E455909
|
entity |
| Predicate | launchPlatformRole |
P132887
|
FINISHED |
| Object | fleet air defense |
—
|
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: fleet air defense | Statement: [AIM-54 Phoenix, launchPlatformRole, fleet air defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchPlatformRole Context triple: [AIM-54 Phoenix, launchPlatformRole, fleet air defense]
-
A.
launchPlatformFor
Indicates a relationship where one entity serves as the platform or site from which another entity is launched.
-
B.
launchPlatformName
Indicates the name of the platform or site from which a launch (typically of a vehicle, rocket, or mission) is conducted.
-
C.
launchPlatformVariant
Indicates a relationship where one entity serves as a specific version or type of platform from which another entity is launched.
-
D.
platformRole
Indicates the specific function, position, or level of responsibility an entity holds within a given platform or system.
-
E.
launchProfile
Indicates initiating or configuring the conditions, parameters, or settings under which a launch or execution process is carried out.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55010d27c8190aad8d3c9e8cd31b2 |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:47 a.m.