Triple
T32073475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Force de frappe |
E819077
|
entity |
| Predicate | nuclearTestSites |
P10784
|
FINISHED |
| Object | Algerian Sahara |
—
|
NE NERFINISHED |
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: Algerian Sahara | Statement: [Force de frappe, nuclearTestSites, Algerian Sahara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearTestSites Context triple: [Force de frappe, nuclearTestSites, Algerian Sahara]
-
A.
nuclearTestSiteFor
chosen
Indicates that a location serves or served as a site where a particular entity conducts or conducted nuclear weapons testing.
-
B.
nuclearTestTarget
Indicates that an entity is the target or location where a nuclear test is conducted.
-
C.
nuclearTestedAs
Indicates that an entity has been subjected to or involved in a nuclear test in the role or manner specified by the related entity.
-
D.
firstNuclearTestLocation
Indicates the place where an entity conducted its first nuclear test.
-
E.
nuclearTestSeries
Indicates a relationship where multiple nuclear tests are grouped and conducted as part of a coordinated series or campaign.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:23 a.m.