Triple
T37904248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spanish Antarctica |
E945504
|
entity |
| Predicate | nuclearFree |
P65224
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Spanish Antarctica, nuclearFree, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearFree Context triple: [Spanish Antarctica, nuclearFree, true]
-
A.
isNonNuclear
Indicates that something does not involve, contain, or relate to nuclear weapons, nuclear power, or nuclear materials.
-
B.
nuclearPowered
Indicates that something operates using nuclear energy as its primary power source.
-
C.
nuclearWeapon
Indicates that an entity possesses, involves, or is characterized by nuclear weapons or nuclear-weapon-related capabilities.
-
D.
nuclearPolicy
Indicates the stance, rules, or strategic approach an entity adopts regarding the development, possession, deployment, or use of nuclear weapons or nuclear technology.
-
E.
designatedNuclearFreeZone
chosen
Indicates that a location or area has been officially declared as prohibiting the presence, development, or deployment of nuclear weapons or nuclear-related activities.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.