Triple
T25259305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazagon Dock Shipbuilders Limited |
E633259
|
entity |
| Predicate | notableVesselBuilt |
P184829
|
FINISHED |
| Object | INS Kolkata |
—
|
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: INS Kolkata | Statement: [Mazagon Dock Shipbuilders Limited, notableVesselBuilt, INS Kolkata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVesselBuilt Context triple: [Mazagon Dock Shipbuilders Limited, notableVesselBuilt, INS Kolkata]
-
A.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
B.
namedVesselOf
Indicates that one entity is the specific named vessel (e.g., ship, boat, or craft) associated with or belonging to another entity.
-
C.
vesselLaunched
Indicates that a vessel has been formally set afloat or put into operation at a specific time or place.
-
D.
notableShipOnRoute
Indicates that a particular ship is especially significant or prominent among those operating on a given route.
-
E.
vesselDesignation
Indicates that a specific identifying designation (such as a name, number, or code) is assigned to a vessel.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: April 21, 2026, 1:13 p.m.