Triple
T14638476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dothraki Sea |
E343663
|
entity |
| Predicate | travelHazards |
P115167
|
FINISHED |
| Object | raiding khalasars |
—
|
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: raiding khalasars | Statement: [Dothraki Sea, travelHazards, raiding khalasars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelHazards Context triple: [Dothraki Sea, travelHazards, raiding khalasars]
-
A.
travelAdvisory
Indicates that one authority issues guidance or warnings to others about safety, risks, or conditions related to traveling to a particular place.
-
B.
hasNaturalHazardRisk
Indicates that an entity is exposed or subject to potential damage or impact from one or more natural hazards (e.g., earthquakes, floods, storms).
-
C.
riskToEarth
Indicates that something poses a potential threat, danger, or harmful impact to Earth.
-
D.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
-
E.
frequentNaturalHazard
Indicates that a location or area regularly experiences natural hazards such as floods, earthquakes, storms, or similar events with notable frequency.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4aca6448190adf1042dfbfef716 |
completed | April 14, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:26 a.m.