Triple
T35108934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VR-3 Reys |
E1013230
|
entity |
| Predicate | hasRussianServiceDesignation |
P158134
|
FINISHED |
| Object | VR-3 |
—
|
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: VR-3 | Statement: [VR-3 Reys, hasRussianServiceDesignation, VR-3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRussianServiceDesignation Context triple: [VR-3 Reys, hasRussianServiceDesignation, VR-3]
-
A.
russianDesignation
chosen
Indicates that one entity is the Russian-language name, label, or designation used to refer to another entity.
-
B.
SovietDesignation
Indicates that an entity has been assigned an official designation or code name by Soviet authorities or according to Soviet classification systems.
-
C.
hullNumberInRussianService
Indicates that an entity has a specific hull identification number assigned to it while in Russian naval service.
-
D.
hasRussianVersion
Indicates that something has a corresponding version or counterpart that is in the Russian language.
-
E.
hasMilitaryDesignation
Indicates that an entity is assigned a specific military-related code, title, or classification.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.