Triple
T29562308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackbriar |
E750069
|
entity |
| Predicate | coverStatus |
P178607
|
FINISHED |
| Object | plausibly deniable |
—
|
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: plausibly deniable | Statement: [Blackbriar, coverStatus, plausibly deniable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverStatus Context triple: [Blackbriar, coverStatus, plausibly deniable]
-
A.
coverPosition
Indicates that one entity occupies or shields a specific position or area, providing coverage for it.
-
B.
coverText
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
-
C.
coverVersionBy
Indicates that one creative work is a cover version performed or produced by a particular artist or entity.
-
D.
coversFrom
Indicates that one entity provides protection, concealment, or shelter for another entity against something originating from a specified source or direction.
-
E.
cover
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 28, 2026, 5:20 p.m.