Triple
T31107154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Monarch (nuclear testing cover) |
E792824
|
entity |
| Predicate | isCovert |
P92521
|
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: [Project Monarch (nuclear testing cover), isCovert, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCovert Context triple: [Project Monarch (nuclear testing cover), isCovert, true]
-
A.
isCove
Indicates that one location or geographic feature is a small, sheltered bay or inlet along a coastline or shore.
-
B.
secretlyIs
Indicates that one entity possesses a hidden or undisclosed identity, role, or attribute in relation to another entity.
-
C.
covertRole
chosen
Indicates that an entity holds or performs a hidden, secret, or undercover role in relation to another entity or context.
-
D.
coerces
Indicates that one entity forces or pressures another entity to act against their will or better judgment.
-
E.
isCoherent
Indicates that the elements of something are logically consistent, well-organized, and fit together in a unified, intelligible way.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:03 p.m.