Triple
T7434653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Almond Valley (Scottish Parliament constituency) |
E171580
|
entity |
| Predicate | regionSeatsCount |
P76381
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Almond Valley (Scottish Parliament constituency), regionSeatsCount, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionSeatsCount Context triple: [Almond Valley (Scottish Parliament constituency), regionSeatsCount, 7]
-
A.
individualSeats
Indicates that an entity provides or consists of separate, single-person seating positions rather than shared or bench-style seating.
-
B.
numberOfCommonsSeats
Indicates the number of seats an entity holds or is allocated in the House of Commons.
-
C.
numberOfSeatingRows
Indicates the total count of seating rows associated with an entity, such as a venue, vehicle, or seating area.
-
D.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
E.
seatCount
Indicates the number of seats associated with an entity, such as a venue, vehicle, or room.
- 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_69c68a64228c8190affaec2a8127ce7b |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f328cf6081908bea065639fd3620 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f038582c8190bac77c9b5a34b862 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f0be2b1c8190bea06100a7caef2b |
completed | March 27, 2026, 9:03 p.m. |
Created at: March 27, 2026, 3:13 p.m.