Triple
T25259311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mazagon Dock Shipbuilders Limited |
E633259
|
entity |
| Predicate | notableSubmarineBuilt |
P184829
|
FINISHED |
| Object | INS Kalvari |
—
|
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 Kalvari | Statement: [Mazagon Dock Shipbuilders Limited, notableSubmarineBuilt, INS Kalvari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSubmarineBuilt Context triple: [Mazagon Dock Shipbuilders Limited, notableSubmarineBuilt, INS Kalvari]
-
A.
notableVesselBuilt
chosen
Indicates that a particular vessel was constructed by or for the subject and is notable or significant in that context.
-
B.
submarineClassName
Indicates the specific class designation or type category to which a submarine belongs.
-
C.
submarineClassLeadShip
Indicates that one entity is the lead (first-built or first-commissioned) ship of a particular submarine class represented by the other entity.
-
D.
submarine
Indicates that one entity is a submarine in relation to another entity or context.
-
E.
antiSubmarineArmament
Indicates the type or presence of weapons or equipment specifically designed for anti-submarine warfare associated with an entity.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 21, 2026, 1:13 p.m.