Triple
T37665912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cascade Kingdom |
E937818
|
entity |
| Predicate | gameRegionType |
P189113
|
FINISHED |
| Object | kingdom |
—
|
LITERAL 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: kingdom | Statement: [Cascade Kingdom, gameRegionType, kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameRegionType Context triple: [Cascade Kingdom, gameRegionType, kingdom]
-
A.
hasPrimaryGameRegion
Indicates that an entity is associated with a main or principal geographic region in which a game is released, played, or targeted.
-
B.
homeGroundRegion
Indicates that a sports team’s primary home venue is located within a specified geographic region.
-
C.
isAvailableInRegion
Indicates that an entity can be accessed, used, or provided within a specified geographic or administrative region.
-
D.
releasePlatformRegion
Indicates the specific geographic region or market where a release (such as a product, service, or media title) is made available on a given platform.
-
E.
isPlayedInRegion
Indicates that an instance of something (such as a game, media, or event) is available to be played or occurs within a specified geographic region.
- F. None of above. chosen
Provenance (4 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:18 p.m.