Triple
T21137167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lop Nur |
E520842
|
entity |
| Predicate | nuclearTestCountApproximate |
P42472
|
FINISHED |
| Object | over 40 |
—
|
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: over 40 | Statement: [Lop Nur, nuclearTestCountApproximate, over 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearTestCountApproximate Context triple: [Lop Nur, nuclearTestCountApproximate, over 40]
-
A.
nuclearTestsConducted
Indicates that one entity has carried out nuclear weapons tests involving another entity, location, or time period.
-
B.
numberOfNuclearTests
chosen
Indicates the total count of nuclear tests associated with a given entity (such as a country, site, or time period).
-
C.
nuclearTestedAs
Indicates that an entity has been subjected to or involved in a nuclear test in the role or manner specified by the related entity.
-
D.
nuclearTestSeriesNumber
Indicates the specific sequence or series number assigned to a set of related nuclear tests within a broader testing program.
-
E.
nuclearTestSeries
Indicates a relationship where multiple nuclear tests are grouped and conducted as part of a coordinated series or campaign.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7235b89188190a6209c0a1839ee03 |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:57 p.m.