Triple
T31970205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanker |
E816290
|
entity |
| Predicate | appliesToLaunchPlatform |
P135454
|
FINISHED |
| Object | silo-based ICBM |
—
|
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: silo-based ICBM | Statement: [Spanker, appliesToLaunchPlatform, silo-based ICBM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToLaunchPlatform Context triple: [Spanker, appliesToLaunchPlatform, silo-based ICBM]
-
A.
worksOnPlatform
Indicates that an entity performs its functions, operations, or activities using or within a specified platform.
-
B.
occursOnPlatform
Indicates that an event, action, or process takes place or is carried out on a specified platform.
-
C.
launchesSupported
Indicates that one entity is capable of initiating or starting another entity or process.
-
D.
usedOnPlatformType
chosen
Indicates that something is utilized or operates on a specific type of platform.
-
E.
launchPlatformVariant
Indicates a relationship where one entity serves as a specific version or type of platform from which another entity is launched.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 1, 2026, 12:10 a.m.