Triple
T17080634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RBMK-1000 |
E414458
|
entity |
| Predicate | graphiteMassApproximate |
P7301
|
FINISHED |
| Object | about 1700 tonnes of graphite |
—
|
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 1700 tonnes of graphite | Statement: [RBMK-1000, graphiteMassApproximate, about 1700 tonnes of graphite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphiteMassApproximate Context triple: [RBMK-1000, graphiteMassApproximate, about 1700 tonnes of graphite]
-
A.
approximateMass
chosen
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
B.
approximateWeightInPounds
Indicates the estimated weight of an entity expressed in pounds, rather than an exact measured value.
-
C.
mineCountApproximate
Indicates that the number of mines associated with an entity is estimated or roughly counted rather than known exactly.
-
D.
graphAnalogue
Indicates that one entity serves as a graph-theoretic counterpart or structural analogue of another entity.
-
E.
obtainsMassVia
Indicates that an entity acquires its mass through a specified process, mechanism, or interaction.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe2fe7c819099ab0586b1a119f6 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.