Triple
T29439240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legacy |
E746664
|
entity |
| Predicate | threatEncounteredNear |
P172831
|
FINISHED |
| Object | Kraken |
—
|
NE NERFINISHED |
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: Kraken | Statement: [Legacy, threatEncounteredNear, Kraken]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatEncounteredNear Context triple: [Legacy, threatEncounteredNear, Kraken]
-
A.
threatContained
Indicates that an identified threat has been successfully neutralized, controlled, or otherwise prevented from causing further harm or escalation.
-
B.
threatTypeEngaged
Indicates that an entity has actively engaged with or responded to a specific type of threat.
-
C.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
D.
threatInStory
Indicates that one entity poses or represents a danger, menace, or harmful intent toward another entity within the context of a narrative or story.
-
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. 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 28, 2026, 3:20 p.m.