Triple
T34918763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VVER-440 |
E1007077
|
entity |
| Predicate | firstCommercialOperationCountry |
P152846
|
FINISHED |
| Object | Soviet Union |
E363
|
NE 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: Soviet Union | Statement: [VVER-440, firstCommercialOperationCountry, Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCommercialOperationCountry Context triple: [VVER-440, firstCommercialOperationCountry, Soviet Union]
-
A.
firstCommercialNetworkCountry
Indicates the country where a given entity first launched or operated its commercial network.
-
B.
operatedByCountry
Indicates that an entity (such as an organization, facility, or service) is run, managed, or controlled by a specific country or its government.
-
C.
operatedToCountry
Indicates that an operation, service, or activity is conducted or extended from some source to a specified country.
-
D.
wasFirstPerformedInCountry
chosen
Indicates that an action, event, or work was first performed within the borders of a specified country.
-
E.
countryOfFirstMarketing
Indicates the country where a product was first introduced or made available on the market.
- F. None of above.
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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37d9341d048190b0f208e97fa0eba5 |
completed | June 21, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.