Triple
T28016447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian nuclear power program |
E707555
|
entity |
| Predicate | exportModel |
P165115
|
FINISHED |
| Object | build-own-operate |
—
|
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: build-own-operate | Statement: [Russian nuclear power program, exportModel, build-own-operate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportModel Context triple: [Russian nuclear power program, exportModel, build-own-operate]
-
A.
namespaceModel
Indicates a relationship where a model is defined within, or associated with, a particular namespace or logical grouping.
-
B.
modelIn
Indicates that one entity serves as a representation or simulation of another entity.
-
C.
model
Indicates that one entity serves as a representation, example, or simulation of another entity or concept.
-
D.
testedModel
Indicates that an entity has evaluated or examined a particular model to assess its performance, behavior, or validity.
-
E.
possibleModel
Indicates that one entity can serve as a potential or candidate model or template for another entity.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 8:07 p.m.