Triple
T504444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom Shopping Centre |
E10471
|
entity |
| Predicate | isMajorCentreFor |
P164
|
FINISHED |
| Object | shopping in Glenrothes |
—
|
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: shopping in Glenrothes | Statement: [Kingdom Shopping Centre, isMajorCentreFor, shopping in Glenrothes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorCentreFor Context triple: [Kingdom Shopping Centre, isMajorCentreFor, shopping in Glenrothes]
-
A.
isMajorCenterOf
chosen
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
B.
hasPopulationCenterType
Indicates the classification of a population center by its type, such as city, town, village, or other settlement category.
-
C.
hasMajorCity
Indicates that a location possesses at least one city of significant size, importance, or influence within its region or country.
-
D.
hasPopulationCenter
Indicates that an area, region, or administrative unit contains or is served by a primary settlement or population hub.
-
E.
majorPopulationCenter
Indicates that a location functions as a primary hub of population concentration and activity within a region.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f149bd1c81908ff58ac504ace2bf |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfce7a08190a408bc019de60d5d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.