Triple
T32822222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department S |
E839463
|
entity |
| Predicate | usedCoverTypes |
P10512
|
FINISHED |
| Object | false identities |
—
|
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: false identities | Statement: [Department S, usedCoverTypes, false identities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCoverTypes Context triple: [Department S, usedCoverTypes, false identities]
-
A.
usedCover
Indicates that one entity employed another entity as a protective or concealing cover in a given context.
-
B.
hasCoverType
chosen
Indicates that one entity possesses or is associated with a specific type or category of cover.
-
C.
coversMaterialType
Indicates that one entity includes, addresses, or applies to a specified type of material.
-
D.
supportsCustomCovers
Indicates that one entity provides the capability for another entity to use or define custom cover designs or images.
-
E.
brandCovered
Indicates that one entity provides coverage, representation, or inclusion for a particular brand within its scope (e.g., in a policy, service, catalog, or offering).
- 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_69f3493df9008190a8f5d843dcd77704 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:15 a.m.