Triple
T10823580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewisham East |
E255436
|
entity |
| Predicate | isSafeLabourSeat |
P75353
|
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: [Lewisham East, isSafeLabourSeat, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSafeLabourSeat Context triple: [Lewisham East, isSafeLabourSeat, true]
-
A.
isSafeSeatFor
Indicates that one entity is a suitable and secure seating option for another entity, posing no unacceptable risk or harm.
-
B.
hasBeenSafeSeatFor
chosen
Indicates that a political position or constituency has consistently been held securely by a particular party or candidate, with little risk of losing it in elections.
-
C.
seatIs
Indicates that one entity functions as the seat or seating position of another entity.
-
D.
canSitIn
Indicates that one entity is able or permitted to sit inside or occupy the seating space of another entity.
-
E.
safetyPositioning
Indicates the spatial or situational arrangement of entities to ensure or enhance safety.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734cf7918819094d36ea208c80d12 |
completed | April 9, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.