Triple
T20912569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semipalatinsk Test Site |
E514983
|
entity |
| Predicate | numberOfUndergroundTests |
P10947
|
FINISHED |
| Object | over 300 |
—
|
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 300 | Statement: [Semipalatinsk Test Site, numberOfUndergroundTests, over 300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfUndergroundTests Context triple: [Semipalatinsk Test Site, numberOfUndergroundTests, over 300]
-
A.
numberOfUndergroundStations
Indicates the total count of underground (subway/metro) stations associated with a given entity.
-
B.
numberOfTests
chosen
Indicates the quantity of tests associated with or performed in a given context or entity.
-
C.
hasUndergroundLength
Indicates the extent of an object or structure that lies below ground level, measured as its underground length.
-
D.
plannedNumberOfTests
Indicates the total count of tests that are intended or scheduled to be conducted for a given context or period.
-
E.
operatedUnderground
Indicates that an entity conducted its activities or operations beneath the surface of the ground, rather than at or above ground level.
- 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_69e0b4f9d5ec8190bb2bd27350ed341c |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6ec5f5bc48190a8e7e6af60b158fb |
completed | April 21, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:48 p.m.