Triple
T31704750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sting Ray torpedo |
E809147
|
entity |
| Predicate | launchShipExample |
P176777
|
FINISHED |
| Object | Type 23 frigate |
—
|
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: Type 23 frigate | Statement: [Sting Ray torpedo, launchShipExample, Type 23 frigate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchShipExample Context triple: [Sting Ray torpedo, launchShipExample, Type 23 frigate]
-
A.
commandsShip
Indicates that one entity has authority over and directs the operation of a ship.
-
B.
mainShip
Indicates that one entity serves as the primary or principal ship associated with another entity.
-
C.
shipDraft
Indicates the depth of a ship’s hull below the waterline, typically representing how deeply the vessel sits in the water.
-
D.
firstShip
Indicates that the subject is the earliest or initial ship associated with, created by, or used in relation to the object.
-
E.
componentShip
Indicates that one entity is a physical or logical component or part of another entity, such that the whole is composed of or depends on that component.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 30, 2026, 11:13 p.m.