Triple
T37371640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dimona reactor |
E927858
|
entity |
| Predicate | inspections |
P187791
|
FINISHED |
| Object | not open to routine international inspections |
—
|
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: not open to routine international inspections | Statement: [Dimona reactor, inspections, not open to routine international inspections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspections Context triple: [Dimona reactor, inspections, not open to routine international inspections]
-
A.
inspectionAuthority
Indicates that one entity has the official power or responsibility to inspect, examine, or audit another entity or its activities.
-
B.
inspectionRequired
Indicates that an entity must undergo an inspection before it can proceed, be used, or be approved.
-
C.
inspectionFrequency
Indicates how often an entity is examined, checked, or reviewed within a given time period.
-
D.
isInspected
Indicates that an entity is examined or checked by another entity to assess its condition, quality, or compliance.
-
E.
usesInspectors
Indicates that one entity employs or relies on inspectors to examine, verify, or assess another entity or its activities.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb8c37931c81909da038c18ed9add2 |
completed | May 6, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.