Triple
T14617120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visakhapatnam-class destroyer |
E343113
|
entity |
| Predicate | commissioningOfLeadShip |
P75757
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [Visakhapatnam-class destroyer, commissioningOfLeadShip, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissioningOfLeadShip Context triple: [Visakhapatnam-class destroyer, commissioningOfLeadShip, 2021]
-
A.
commissionedShip
Indicates that a ship has been formally placed into active service, typically following its construction or acquisition.
-
B.
shipCommissionedAs
Indicates that a ship entered active service under a specific name or designation at the time of its commissioning.
-
C.
expectedCommissioningOfLeadBoat
chosen
Indicates the scheduled or anticipated date or event when the first (lead) boat in a series is formally commissioned into service.
-
D.
classLeadShip
Indicates a leadership relationship where one entity serves as the leading or primary representative of a class, group, or category.
-
E.
leadShip
Indicates that one entity serves as the commander or person in charge of a ship belonging to or associated with another 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb46439b88190a4affcc7ccedab6b |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.