Triple
T33098077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet aircraft carrier Baku |
E846964
|
entity |
| Predicate | hullNumberInSovietService |
P175804
|
FINISHED |
| Object | Baku |
—
|
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: Baku | Statement: [Soviet aircraft carrier Baku, hullNumberInSovietService, Baku]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hullNumberInSovietService Context triple: [Soviet aircraft carrier Baku, hullNumberInSovietService, Baku]
-
A.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
-
B.
hullNumberReusedFrom
Indicates that a vessel’s hull number was previously assigned to another vessel and has been reused from that earlier assignment.
-
C.
SovietDesignation
Indicates that an entity has been assigned an official designation or code name by Soviet authorities or according to Soviet classification systems.
-
D.
hullNumberInFilm
Indicates that a specific hull number is shown or referenced within a particular film.
-
E.
hullConstruction
Indicates the process or activity of building, assembling, or forming the main body (hull) of a vessel or similar structure.
- 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_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:26 a.m.