Triple
T37592034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Kurast |
E935282
|
entity |
| Predicate | hasEnvironmentalHazard |
P196347
|
FINISHED |
| Object | tight spaces for ranged attacks |
—
|
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: tight spaces for ranged attacks | Statement: [Upper Kurast, hasEnvironmentalHazard, tight spaces for ranged attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnvironmentalHazard Context triple: [Upper Kurast, hasEnvironmentalHazard, tight spaces for ranged attacks]
-
A.
hasEnvironmentalRisk
Indicates that an entity poses, contributes to, or is associated with potential harm or adverse impact on the environment.
-
B.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
-
C.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
D.
hasHazardLevel
Indicates that an entity is associated with a specified degree or category of risk or danger.
-
E.
isHazard
Indicates that something poses a potential risk, danger, or harmful condition to people, property, or the 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
| PDg | Predicate description generation | batch_69fe21afdc4c8190913ac4b55a9a5f52 |
completed | May 8, 2026, 5:47 p.m. |
Created at: May 3, 2026, 4:18 p.m.