Triple
T31107167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Monarch (nuclear testing cover) |
E792824
|
entity |
| Predicate | usesCoverLocationType |
P191015
|
FINISHED |
| Object | nuclear test sites |
—
|
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: nuclear test sites | Statement: [Project Monarch (nuclear testing cover), usesCoverLocationType, nuclear test sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCoverLocationType Context triple: [Project Monarch (nuclear testing cover), usesCoverLocationType, nuclear test sites]
-
A.
coverLocation
Indicates that one entity serves as a covering or protective layer positioned at or over a specific location of another entity.
-
B.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
-
C.
isCoveredSpace
Indicates that one space or area is physically sheltered or enclosed by another structure or surface.
-
D.
usedCover
Indicates that one entity employed another entity as a protective or concealing cover in a given context.
-
E.
isCoverableOn
Indicates that one entity can be placed over another in such a way that it fully or suitably covers it.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd866dd248190bff61c43bee93f54 |
completed | May 7, 2026, 6:22 p.m. |
Created at: April 29, 2026, 9:03 p.m.