Triple
T38643434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twilight Highlands |
E938658
|
entity |
| Predicate | capitalHubHorde |
P94182
|
FINISHED |
| Object | Dragonmaw Port |
—
|
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: Dragonmaw Port | Statement: [Twilight Highlands, capitalHubHorde, Dragonmaw Port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalHubHorde Context triple: [Twilight Highlands, capitalHubHorde, Dragonmaw Port]
-
A.
capitalWithinHorde
Indicates that a capital city is located within the territorial domain or control of a particular horde.
-
B.
EventHorizonLocations
Indicates the spatial positions or regions where an event horizon exists or is defined.
-
C.
isCentralHubOf
chosen
Indicates that one entity functions as the primary connecting or coordinating hub for activities, resources, or interactions among multiple other entities.
-
D.
cityHeld
Indicates that a particular city was the location where an event, activity, or occurrence took place or was hosted.
-
E.
cityCenterStatus
Indicates whether a location holds the status of being the central or main area of a city.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 3, 2026, 4:32 p.m.