Triple
T36875121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Île Longue naval base |
E911321
|
entity |
| Predicate | nuclearWeaponsRelated |
P173488
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Île Longue naval base, nuclearWeaponsRelated, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearWeaponsRelated Context triple: [Île Longue naval base, nuclearWeaponsRelated, yes]
-
A.
nuclearWeapon
chosen
Indicates that an entity possesses, involves, or is characterized by nuclear weapons or nuclear-weapon-related capabilities.
-
B.
nuclearWeaponsProgram
Indicates the existence, development, or pursuit of a program related to the research, production, or maintenance of nuclear weapons.
-
C.
positionOnNuclearWeapons
Indicates a stance, policy, or viewpoint that an entity holds regarding the development, possession, use, or regulation of nuclear weapons.
-
D.
nuclearWeaponConfiguration
Indicates the specific arrangement, setup, or design characteristics associated with a nuclear weapon or nuclear weapons system.
-
E.
nuclearWeaponsState
Indicates that a state possesses, has developed, or is recognized as having nuclear weapons capabilities.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.