Triple
T11425406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suffren-class nuclear attack submarines |
E270733
|
entity |
| Predicate | keelLaidForFirstUnit |
P79986
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Suffren-class nuclear attack submarines, keelLaidForFirstUnit, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keelLaidForFirstUnit Context triple: [Suffren-class nuclear attack submarines, keelLaidForFirstUnit, 2007]
-
A.
keelLaidFor
chosen
Indicates that the initial structural construction (keel laying) of a vessel has been formally started for a particular ship or project.
-
B.
dateOfKeelLaying
Indicates the calendar date on which the keel of a vessel was formally laid, marking the official start of its construction.
-
C.
firstShip
Indicates that the subject is the earliest or initial ship associated with, created by, or used in relation to the object.
-
D.
originalShipLaunchedIn
Indicates that an original ship was first launched in a specified year, place, or context.
-
E.
vesselLaunched
Indicates that a vessel has been formally set afloat or put into operation at a specific time or place.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806be9c2c819084da13101cbb6c81 |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.