Triple
T5697428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevada National Security Site |
E125572
|
entity |
| Predicate | nuclearTestingMoratorium |
P42481
|
FINISHED |
| Object | since early 1990s |
—
|
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: since early 1990s | Statement: [Nevada National Security Site, nuclearTestingMoratorium, since early 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearTestingMoratorium Context triple: [Nevada National Security Site, nuclearTestingMoratorium, since early 1990s]
-
A.
nuclearTestingPeriod
Indicates the time span during which nuclear tests are conducted or in effect.
-
B.
nuclearTestingPeriodEnd
chosen
Indicates the point in time when a specified period of nuclear weapons testing comes to an end.
-
C.
numberOfNuclearTests
Indicates the total count of nuclear tests associated with a given entity (such as a country, site, or time period).
-
D.
firstNuclearTest
Indicates the event in which an entity conducts its first-ever test of a nuclear explosive device.
-
E.
nuclearTestSiteFor
Indicates that a location serves or served as a site where a particular entity conducts or conducted nuclear weapons testing.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0240d6c0c8190bf970c7652fd9573 |
completed | March 22, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:45 p.m.