Triple
T12607968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kahuta uranium enrichment plant |
E301032
|
entity |
| Predicate | cameToProminence |
P51037
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Kahuta uranium enrichment plant, cameToProminence, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameToProminence Context triple: [Kahuta uranium enrichment plant, cameToProminence, 1980s]
-
A.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
B.
helpedPropelToMainstreamFame
Indicates that one entity significantly contributed to another entity’s rise to widespread public recognition or mainstream popularity.
-
C.
roseToProminenceIn
chosen
Indicates the time or context in which an entity became widely recognized, influential, or notable.
-
D.
wasProminentIn
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
-
E.
inceptionOfNotoriety
Indicates the point or event at which an entity first becomes widely known or gains significant public notoriety.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:11 p.m.