Triple
T35343624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clydebank and Milngavie |
E1020675
|
entity |
| Predicate | parliamentaryNameLanguage |
P183043
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Clydebank and Milngavie, parliamentaryNameLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentaryNameLanguage Context triple: [Clydebank and Milngavie, parliamentaryNameLanguage, English]
-
A.
languageOfLegislature
Indicates the language or languages officially used by a legislature to conduct its proceedings, draft laws, and perform its formal functions.
-
B.
officialLanguageOfNomination
Indicates the language officially used in the nomination process or documentation for a given entity.
-
C.
hasLanguageOfOfficialName
Indicates that an entity’s official name is expressed in a specified language.
-
D.
languageOfBallots
Indicates the language or languages in which ballots are written or presented.
-
E.
officialLanguage
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
- 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_69f76debb4e08190be52d89b8af2392d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.