Triple
T3285636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bureau for Paranormal Research and Defense |
E68974
|
entity |
| Predicate | typeOfThreatsHandled |
P19863
|
FINISHED |
| Object | supernatural threats |
—
|
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: supernatural threats | Statement: [Bureau for Paranormal Research and Defense, typeOfThreatsHandled, supernatural threats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfThreatsHandled Context triple: [Bureau for Paranormal Research and Defense, typeOfThreatsHandled, supernatural threats]
-
A.
recognizesThreat
Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
-
B.
threatTypeAddressed
chosen
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
-
C.
countermeasuresFaced
Indicates that one entity has encountered or had to deal with countermeasures implemented by another entity.
-
D.
facesThreat
Indicates that an entity is exposed to or confronted by a potential danger, risk, or harmful situation.
-
E.
threatTypeMonitored
Indicates that a particular type of threat is being actively observed, tracked, or watched for by some monitoring process or system.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb03918c48190987d7cfd3bda9716 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.