Triple
T32919590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R-39 Rif |
E842107
|
entity |
| Predicate | launchPlatformClass |
P88551
|
FINISHED |
| Object | Typhoon-class SSBN |
—
|
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: Typhoon-class SSBN | Statement: [R-39 Rif, launchPlatformClass, Typhoon-class SSBN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchPlatformClass Context triple: [R-39 Rif, launchPlatformClass, Typhoon-class SSBN]
-
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
chosen
Indicates a relationship where one entity serves as a specific version or type of platform from which another entity is launched.
-
D.
launcherType
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
-
E.
launchPlatformRole
Indicates the functional role or responsibility an entity has in relation to a launch platform within a launch or deployment context.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 1:19 a.m.