Triple
T29494106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Royal Sovereign (05) |
E748167
|
entity |
| Predicate | returnedFromSovietUnion |
P179932
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [HMS Royal Sovereign (05), returnedFromSovietUnion, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedFromSovietUnion Context triple: [HMS Royal Sovereign (05), returnedFromSovietUnion, 1949]
-
A.
statusInSovietUnion
Indicates the legal, social, or political standing an entity held within the Soviet Union.
-
B.
isSovietCounterpartOf
Indicates that one entity serves as the Soviet-era equivalent or counterpart to another entity in role, function, or status.
-
C.
successorStateOnSovietSide
Indicates that one state is recognized as the political or legal successor to a former state that was part of the Soviet sphere or structure.
-
D.
homeCountryDuringSovietEra
Indicates the country that was considered an entity’s home country during the period of the Soviet Union’s existence.
-
E.
formerSovietRepublic
Indicates that an entity is a country or region that was once part of the Soviet Union but is now independent.
- 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: April 28, 2026, 4:17 p.m.