Triple
T24318619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copland Road Stand |
E612892
|
entity |
| Predicate | locatedInCityCouncilArea |
P962
|
FINISHED |
| Object | Glasgow City |
—
|
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 City | Statement: [Copland Road Stand, locatedInCityCouncilArea, Glasgow City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCityCouncilArea Context triple: [Copland Road Stand, locatedInCityCouncilArea, Glasgow City]
-
A.
locatedInRegionalCouncil
Indicates that one entity is geographically situated within the jurisdictional area governed by a specific regional council.
-
B.
isRepresentedInCityCouncilBy
Indicates that a person or group has a designated representative who serves on the city council on their behalf.
-
C.
hasCouncilDistrict
chosen
Indicates that an entity is located within or represented by a specific council district.
-
D.
locatedInProvincialElectoralDistrict
Indicates that one entity is situated within the boundaries of a specific provincial electoral district.
-
E.
meetsInDistrict
Indicates that two or more entities hold a meeting within the boundaries of a specified administrative district.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292a916c8819096d018e7ffaf483b |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:47 a.m.