Triple
T38643433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twilight Highlands |
E938658
|
entity |
| Predicate | capitalHubAlliance |
P94182
|
FINISHED |
| Object | Highbank |
—
|
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: Highbank | Statement: [Twilight Highlands, capitalHubAlliance, Highbank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalHubAlliance Context triple: [Twilight Highlands, capitalHubAlliance, Highbank]
-
A.
connectsCapitalWith
Indicates a relationship where something serves as a link or route between a capital city and another place or entity.
-
B.
capitalRenamedFrom
Indicates that a capital city previously had a different name, specifying the former name from which it was renamed.
-
C.
capitalRenamedTo
Indicates that a place’s status or name as a capital city has been changed to a new capital designation or name.
-
D.
capitalPossiblyAt
Indicates a possible or uncertain capital relationship, where one location may be the capital of another but this is not definitively established.
-
E.
isCentralHubOf
chosen
Indicates that one entity functions as the primary connecting or coordinating hub for activities, resources, or interactions among multiple other entities.
- 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_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:32 p.m.