Triple
T11835183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bury North |
E281496
|
entity |
| Predicate | isMarginalSeat |
P101751
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bury North, isMarginalSeat, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMarginalSeat Context triple: [Bury North, isMarginalSeat, true]
-
A.
isAtLargeSeat
Indicates that an individual holds or occupies an at-large seat, representing a broad constituency rather than a specific district or sub-area.
-
B.
hasSeatsForConstituency
Indicates that a governing body or institution allocates or provides a certain number of representative seats for a specific constituency.
-
C.
hasSeatAt
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
-
D.
isSafeSeatFor
Indicates that one entity is a suitable and secure seating option for another entity, posing no unacceptable risk or harm.
-
E.
notableSeat
Indicates that an entity holds or is associated with a seat, position, or place that is considered notable or significant in some context.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a62e7e408190998bebe346c82e89 |
completed | April 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.