Triple
T38582559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broken Isles |
E932275
|
entity |
| Predicate | hasCapitalHub |
P58420
|
FINISHED |
| Object | Dalaran (Broken Isles) |
—
|
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: Dalaran (Broken Isles) | Statement: [Broken Isles, hasCapitalHub, Dalaran (Broken Isles)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalHub Context triple: [Broken Isles, hasCapitalHub, Dalaran (Broken Isles)]
-
A.
hasMajorHubIn
Indicates that an entity maintains a primary or significant operational hub or center in a specified location.
-
B.
isCentralHubOf
Indicates that one entity functions as the primary connecting or coordinating hub for activities, resources, or interactions among multiple other entities.
-
C.
hasCapitalConnected
chosen
Indicates that there is a direct connection or linkage between an entity and its capital city.
-
D.
locatedInHubOf
Indicates that one entity is situated within the central hub or core area associated with another entity.
-
E.
hasMajorCityHub
Indicates that an entity contains or is associated with a primary, high-importance city that functions as a central hub for activity, services, or connectivity.
- 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_6a00717f539c8190b70dd0e72c6f7d24 |
completed | May 10, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_6a00710278fc81908889afdcf459ff01 |
completed | May 10, 2026, 11:50 a.m. |
Created at: May 3, 2026, 4:32 p.m.