Triple
T2822760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakistan nuclear weapons program |
E54847
|
entity |
| Predicate | declaredNuclearWeaponsState |
P43540
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Pakistan nuclear weapons program, declaredNuclearWeaponsState, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaredNuclearWeaponsState Context triple: [Pakistan nuclear weapons program, declaredNuclearWeaponsState, 1998]
-
A.
nuclearWeaponsState
Indicates that a state possesses, has developed, or is recognized as having nuclear weapons capabilities.
-
B.
hasNuclearWeapons
Indicates that the subject possesses or controls nuclear weapons.
-
C.
nuclearArsenalStatus
Indicates the condition or level of development, deployment, or readiness of an entity’s nuclear weapons capability.
-
D.
hasNuclearRole
Indicates that an entity participates in, is responsible for, or holds authority related to nuclear activities, functions, or capabilities.
-
E.
nuclearCapability
Indicates that an entity possesses, develops, or has access to nuclear weapons or the technological capacity to produce them.
- F. None of above. chosen
Provenance (4 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_69ab49e100c0819082a40cb797383243 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abdf15b7288190a03d1193cc0544a6 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd08f2f481908c3da8a9c7a00552 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdf13d2b8819097b8edaaea90dbe2 |
completed | March 7, 2026, 8:17 a.m. |
Created at: March 6, 2026, 9:59 p.m.