Triple
T38383420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hårga |
E893814
|
entity |
| Predicate | safetyForOutsiders |
P191421
|
FINISHED |
| Object | dangerous |
—
|
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: dangerous | Statement: [Hårga, safetyForOutsiders, dangerous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyForOutsiders Context triple: [Hårga, safetyForOutsiders, dangerous]
-
A.
safety
Indicates that an entity provides, ensures, or is associated with protection from harm, danger, or risk for another entity or within a given context.
-
B.
safetyAdvice
Indicates that one entity provides guidance or recommendations to another entity about how to avoid danger or reduce risk in a particular context.
-
C.
safetyCategory
Indicates the classification of something according to its level or type of safety.
-
D.
safetyProfile
Indicates the overall level and characteristics of risk or harm associated with something, typically summarizing how safe it is under specified conditions.
-
E.
safetyContext
Indicates the circumstances, conditions, or environment that affect how safe an action, object, or situation is.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: May 3, 2026, 4:31 p.m.