Triple
T25713670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGU |
E644799
|
entity |
| Predicate | hasHazardCharacteristic |
P159491
|
FINISHED |
| Object | surrounded by mountains |
—
|
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: surrounded by mountains | Statement: [TGU, hasHazardCharacteristic, surrounded by mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHazardCharacteristic Context triple: [TGU, hasHazardCharacteristic, surrounded by mountains]
-
A.
hasHazardCharacteristic
chosen
Indicates that an entity possesses a specific hazardous property, condition, or risk-related characteristic.
-
B.
hasHazardLevel
Indicates that an entity is associated with a specified degree or category of risk or danger.
-
C.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
D.
isHazardTo
Indicates that one entity poses a potential source of danger, harm, or risk to another entity.
-
E.
hasSafetyCharacteristic
Indicates that an entity possesses a specific safety-related property, feature, or attribute.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc6008a4819084116248372fdd78 |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 9:22 p.m.