Triple
T27633598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makerfield |
E696407
|
entity |
| Predicate | safeSeatStatus |
P51443
|
FINISHED |
| Object | generally considered a safe Labour 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: generally considered a safe Labour seat | Statement: [Makerfield, safeSeatStatus, generally considered a safe Labour seat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safeSeatStatus Context triple: [Makerfield, safeSeatStatus, generally considered a safe Labour seat]
-
A.
hasSeatStatus
chosen
Indicates the current condition or availability state of a seat in a given context.
-
B.
isSafeSeatFor
Indicates that one entity is a suitable and secure seating option for another entity, posing no unacceptable risk or harm.
-
C.
seatIs
Indicates that one entity functions as the seat or seating position of another entity.
-
D.
seatSince
Indicates that an entity has held a particular seat, position, or place continuously since a specified point in time.
-
E.
seatOwnedBy
Indicates that a particular seat is possessed or held in ownership by a specific 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63125efdc819082d61f5528dcb5b4 |
completed | May 2, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:22 p.m.