Triple
T33098078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet aircraft carrier Baku |
E846964
|
entity |
| Predicate | hullNumberInRussianService |
P176109
|
FINISHED |
| Object | Admiral Gorshkov |
—
|
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: Admiral Gorshkov | Statement: [Soviet aircraft carrier Baku, hullNumberInRussianService, Admiral Gorshkov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hullNumberInRussianService Context triple: [Soviet aircraft carrier Baku, hullNumberInRussianService, Admiral Gorshkov]
-
A.
hullNumberInSovietService
Indicates that an entity bore a specific hull number while in service with the Soviet Navy or other Soviet maritime forces.
-
B.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
C.
usedHullNumberSystem
Indicates that an entity employed a hull numbering system to identify or classify ships or vessels.
-
D.
hullNumberReusedFrom
Indicates that a vessel’s hull number was previously assigned to another vessel and has been reused from that earlier assignment.
-
E.
hullNumberInFilm
Indicates that a specific hull number is shown or referenced within a particular film.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:26 a.m.