Triple
T34918790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VVER-440 |
E1007077
|
entity |
| Predicate | coreHeight |
P181867
|
FINISHED |
| Object | about 2.5–2.6 m |
—
|
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: about 2.5–2.6 m | Statement: [VVER-440, coreHeight, about 2.5–2.6 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreHeight Context triple: [VVER-440, coreHeight, about 2.5–2.6 m]
-
A.
heightContext
Indicates a contextual or situational relationship that specifies how an entity’s height is defined, measured, or interpreted in a particular setting or frame of reference.
-
B.
structureHeight
Indicates that a structure has a specific vertical measurement or height.
-
C.
platformHeight
Indicates the vertical distance or elevation of a platform relative to a defined reference level.
-
D.
totalHeight
Indicates the combined vertical measurement resulting from adding the heights of one or more entities.
-
E.
heightReference
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782cf61948190b98185d961609554 |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f782c848fc8190baea8c845ca9079f |
completed | May 3, 2026, 5:15 p.m. |
Created at: May 3, 2026, 4 p.m.