Triple
T306513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAUD Report |
E6314
|
entity |
| Predicate | recommended |
P5662
|
FINISHED |
| Object | large-scale uranium enrichment program |
—
|
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: large-scale uranium enrichment program | Statement: [MAUD Report, recommended, large-scale uranium enrichment program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommended Context triple: [MAUD Report, recommended, large-scale uranium enrichment program]
-
A.
implementsRecommendationOf
Indicates that one entity carries out or puts into practice a recommendation that was proposed or issued by another entity.
-
B.
recommendedAction
Indicates that one entity suggests or prescribes a particular action for another entity to take.
-
C.
recommendation
chosen
Indicates that one entity suggests, endorses, or advises another entity as suitable or beneficial for a particular purpose or context.
-
D.
advises
Indicates that one entity provides guidance, recommendations, or counsel to another entity.
-
E.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea313be88190b4441f3ea41a99e2 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93db11881909b07ba5e76d91feb |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.