Triple
T14617051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INS Arihant |
E343112
|
entity |
| Predicate | reactorPower |
P95775
|
FINISHED |
| Object | approximately 83 MW |
—
|
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: approximately 83 MW | Statement: [INS Arihant, reactorPower, approximately 83 MW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactorPower Context triple: [INS Arihant, reactorPower, approximately 83 MW]
-
A.
thermalPower
Indicates the amount of heat energy per unit time that a system, device, or process generates, transfers, or consumes.
-
B.
thermalCapacityPerReactor_MWth
chosen
Indicates the amount of thermal power capacity, measured in megawatts thermal (MWth), associated with each individual reactor.
-
C.
thermalNeutronReactor
Indicates that the subject is a nuclear reactor that operates using thermal (low-energy) neutrons to sustain its fission chain reaction.
-
D.
reactorType
Indicates the specific kind or category of reactor associated with an entity.
-
E.
plannedNumberOfReactors
Indicates the total number of reactors that are intended or scheduled to be built, installed, or operated for a given facility or project.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb46439b88190a4affcc7ccedab6b |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.