Triple
T3295487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dundee East |
E69203
|
entity |
| Predicate | parliamentarySeat |
P2710
|
FINISHED |
| Object | House of Commons seat |
—
|
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: House of Commons seat | Statement: [Dundee East, parliamentarySeat, House of Commons seat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentarySeat Context triple: [Dundee East, parliamentarySeat, House of Commons seat]
-
A.
parliamentaryConstituency
chosen
Indicates that one entity serves as the parliamentary constituency to which the other entity (such as a place or representative) is formally linked or assigned.
-
B.
seatOfCouncil
Indicates that a location serves as the official meeting place or headquarters of a council.
-
C.
legislativeAssemblySeats
Indicates the number of seats an entity holds or is allocated in a legislative assembly.
-
D.
constituency
Indicates that one entity functions as a constituent or component part within the structural or organizational makeup of another entity.
-
E.
parliamentaryConstituencyOfEvent
Indicates the parliamentary constituency within whose boundaries a given event takes place or is associated.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb077c60c81909782be5202ce5a43 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.