Triple
T28612090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mined-Out |
E724188
|
entity |
| Predicate | usesHiddenInformation |
P166492
|
FINISHED |
| Object | hidden mines |
—
|
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: hidden mines | Statement: [Mined-Out, usesHiddenInformation, hidden mines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHiddenInformation Context triple: [Mined-Out, usesHiddenInformation, hidden mines]
-
A.
dataHidden
Indicates that certain data is concealed, inaccessible, or not visible to users or systems under normal conditions.
-
B.
abilityIsSecretFrom
Indicates that one party’s ability or capability is intentionally kept hidden or undisclosed from another specified party.
-
C.
hasHiddenIdentity
Indicates that an entity possesses a secret or concealed identity that is not known to others.
-
D.
hiddenIn
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
E.
hiddenAt
Indicates that one entity is concealed or stored at a specific location or within another entity.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6622808b48190bbabcc75288ab031 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f6617a7e7c81908cfac4a2250797ee |
completed | May 2, 2026, 8:41 p.m. |
Created at: April 28, 2026, 4:30 a.m.