Triple
T38583895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadowmoon Valley |
E932302
|
entity |
| Predicate | hordeHub |
P423
|
FINISHED |
| Object | Shadowmoon Village |
—
|
NE NERFINISHED |
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: Shadowmoon Village | Statement: [Shadowmoon Valley, hordeHub, Shadowmoon Village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hordeHub Context triple: [Shadowmoon Valley, hordeHub, Shadowmoon Village]
-
A.
hubFor
chosen
Indicates that one entity serves as a central node or focal point through which activities, connections, or resources related to another entity are organized or routed.
-
B.
hostRock
Indicates that one rock body serves as the surrounding or enclosing rock in which another geological feature (such as an ore deposit, vein, or intrusion) occurs.
-
C.
formerHubFor
Indicates that one entity previously served as a central or primary hub for another entity but no longer holds that role.
-
D.
harbor
Indicates providing shelter, protection, or refuge for someone or something, often by keeping them in a safe or hidden place.
-
E.
hostCluster
Indicates a relationship where one cluster serves as the hosting or parent environment for another resource, service, or sub-cluster.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.