Triple
T33775888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marianne |
E865515
|
entity |
| Predicate | threatTypeEncountered |
P177680
|
FINISHED |
| Object | supernatural curse |
—
|
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 curse | Statement: [Marianne, threatTypeEncountered, supernatural curse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatTypeEncountered Context triple: [Marianne, threatTypeEncountered, supernatural curse]
-
A.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
B.
threatTypeMonitored
Indicates that a particular type of threat is being actively observed, tracked, or watched for by some monitoring process or system.
-
C.
threatEncounteredNear
Indicates that a threat was encountered in close spatial proximity to a specified reference point or entity.
-
D.
threatTypeEngaged
Indicates that an entity has actively engaged with or responded to a specific type of threat.
-
E.
threatTypeAddressed
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:45 a.m.