Triple
T11288557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edinburgh Southern |
E267261
|
entity |
| Predicate | numberOfConstituenciesInRegion |
P13200
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [Edinburgh Southern, numberOfConstituenciesInRegion, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfConstituenciesInRegion Context triple: [Edinburgh Southern, numberOfConstituenciesInRegion, 9]
-
A.
hasNumberOfConstituencies
chosen
Indicates the specific count of constituencies associated with an entity.
-
B.
electoralRegionSeatCount
Indicates the number of seats allocated to a given electoral region within a representative body or legislature.
-
C.
electoralConstituencies
Indicates a relationship where a geographic or political area is divided into specific electoral constituencies used for representation or voting.
-
D.
constituencyNumber
Indicates the specific electoral or administrative constituency identifier assigned to an entity within a numbered set of constituencies.
-
E.
numberOfRegionalCouncils
Indicates the total count of regional councils associated with a given entity.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e98875a08190b8509fe55e49d52d |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.