Triple
T38585844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frostwolf clan |
E932342
|
entity |
| Predicate | regionOnDraenor |
P202630
|
FINISHED |
| Object | Frostfire Ridge |
E932333
|
NE 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: Frostfire Ridge | Statement: [Frostwolf clan, regionOnDraenor, Frostfire Ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOnDraenor Context triple: [Frostwolf clan, regionOnDraenor, Frostfire Ridge]
-
A.
missionRegion
Indicates the geographic or administrative region in which a mission is carried out or assigned.
-
B.
riverRegion
Indicates that a river is located within, flows through, or is otherwise geographically associated with a particular region.
-
C.
settledRegion
Indicates that an entity has established a lasting presence or habitation within a particular geographic region.
-
D.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
E.
EasternView
Indicates a spatial relationship where one entity is oriented toward, faces, or has a view in the eastern direction relative to another reference point or area.
- F. None of above. chosen
Provenance (5 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00a22e32f481909b6006c5b1cdefd3 |
completed | May 10, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41fd4e9bb88190ac2a670763645453 |
completed | June 29, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_6a00a1bd9c908190b4aa17a61f48126f |
completed | May 10, 2026, 3:18 p.m. |
| PDg | Predicate description generation | batch_6a00a22d837081909f19d1078c4fedad |
completed | May 10, 2026, 3:20 p.m. |
Created at: May 3, 2026, 4:32 p.m.