Triple
T34918781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VVER-440 |
E1007077
|
entity |
| Predicate | earlierVariant |
P60231
|
FINISHED |
| Object | VVER-440/V-230 |
—
|
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: VVER-440/V-230 | Statement: [VVER-440, earlierVariant, VVER-440/V-230]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierVariant Context triple: [VVER-440, earlierVariant, VVER-440/V-230]
-
A.
earlyVersion
Indicates that one entity is an earlier or preliminary version of another entity in a version sequence.
-
B.
earlierVersionProposedBy
Indicates that an earlier version of something (e.g., a document, proposal, or plan) was originally put forward or suggested by a particular agent or entity.
-
C.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
D.
firstVariant
Indicates that the subject is the earliest or primary version among multiple variants of the same entity or item.
-
E.
hasEarlierVersion
chosen
Indicates that one entity is an earlier or prior version of another entity in a version sequence.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4 p.m.