Triple
T8669638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon Ross |
E205761
|
entity |
| Predicate | threatensToReveal |
P83996
|
FINISHED |
| Object | Blackbriar details in print |
—
|
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: Blackbriar details in print | Statement: [Simon Ross, threatensToReveal, Blackbriar details in print]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatensToReveal Context triple: [Simon Ross, threatensToReveal, Blackbriar details in print]
-
A.
threatDisplay
Indicates a behavior or signal by one entity intended to warn, intimidate, or deter another entity without immediate physical attack.
-
B.
penaltyForRevealingSecrets
Indicates that an entity incurs a punishment or negative consequence as a result of disclosing confidential or secret information.
-
C.
revealsMurderTo
Indicates that one entity discloses information about a murder to another entity.
-
D.
revealedBefore
Indicates that one entity becomes known, disclosed, or made apparent earlier in time than another entity.
-
E.
threatStatus
Indicates the level or category of risk or danger posed by one entity to another or to a defined system or environment.
- 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4917cb9881909a73b74e54250613 |
completed | March 31, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:31 p.m.