Triple
T26802152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strathclyde valley |
E671129
|
entity |
| Predicate | modernUrbanCentre |
P48921
|
FINISHED |
| Object | Glasgow |
—
|
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: Glasgow | Statement: [Strathclyde valley, modernUrbanCentre, Glasgow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernUrbanCentre Context triple: [Strathclyde valley, modernUrbanCentre, Glasgow]
-
A.
modernCityIs
Indicates that something possesses the characteristics or status of being a modern city.
-
B.
isUrbanCentreFor
Indicates that one place functions as the primary urban hub or central city serving another area or population.
-
C.
urbanCoreCity
Indicates that a city functions as the primary urban core or central city within a larger metropolitan or urban area.
-
D.
urbanCenterDevelopedInto
Indicates that an urban center transformed or evolved over time into another, more developed or differently structured urban center.
-
E.
majorUrbanCenterIn
chosen
Indicates that a city or metropolitan area functions as a primary or significant urban center within the specified region or administrative unit.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 4:23 a.m.