Triple
T14025102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamorta-class corvette |
E337435
|
entity |
| Predicate | firstShipCommissioningDate |
P34263
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Kamorta-class corvette, firstShipCommissioningDate, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstShipCommissioningDate Context triple: [Kamorta-class corvette, firstShipCommissioningDate, 2014]
-
A.
shipCommissionedAs
Indicates that a ship entered active service under a specific name or designation at the time of its commissioning.
-
B.
thirdShipLaunched
Indicates that an entity is the third ship to be launched in a particular sequence or context.
-
C.
commissionedInService
Indicates that an entity was formally brought into active service or duty within a particular organization, role, or context.
-
D.
firstReactorCommissioned
Indicates that the first reactor in a given context has been officially brought into operation or commissioned.
-
E.
firstShip
chosen
Indicates that the subject is the earliest or initial ship associated with, created by, or used in relation to the object.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fa6ca7481908976ce748a1957b1 |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.