Triple
T15614217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mk 15 Snakeye fin |
E375370
|
entity |
| Predicate | retardationMethod |
P119436
|
FINISHED |
| Object | aerodynamic fin drag |
—
|
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: aerodynamic fin drag | Statement: [Mk 15 Snakeye fin, retardationMethod, aerodynamic fin drag]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retardationMethod Context triple: [Mk 15 Snakeye fin, retardationMethod, aerodynamic fin drag]
-
A.
retentionMethod
Indicates the method or strategy used to retain or keep something (such as data, customers, or resources) over time.
-
B.
methodOfRejuvenation
Indicates a process or technique used to restore youthfulness, vitality, or an earlier optimal state to something or someone.
-
C.
realizationMethod
Indicates the means, process, or technique by which something is carried out, implemented, or brought into effect.
-
D.
delayed
Indicates that an expected event, action, or outcome occurred later than its scheduled or usual time.
-
E.
terminationImplementedIn
Indicates that a specific termination or ending process is realized, carried out, or embodied within a particular implementation or system.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e83407c8190abbcd4b7fab0ff85 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:13 a.m.