Triple
T8000412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henley (UK Parliament constituency) |
E186233
|
entity |
| Predicate | hasSafeSeatStatusSince |
P75353
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [Henley (UK Parliament constituency), hasSafeSeatStatusSince, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSafeSeatStatusSince Context triple: [Henley (UK Parliament constituency), hasSafeSeatStatusSince, late 20th century]
-
A.
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.
-
B.
hasSeatStatus
Indicates the current condition or availability state of a seat in a given context.
-
C.
isSafeSeatFor
Indicates that one entity is a suitable and secure seating option for another entity, posing no unacceptable risk or harm.
-
D.
hasHistoricalSeat
Indicates that an entity possesses or is associated with a historically significant seat, location, or place of authority.
-
E.
hasPedestrianStatusSince
Indicates that an entity has held a particular pedestrian-related status continuously starting from a specified point in time.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c9b67988190a8a4a2c960017400 |
completed | March 31, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:17 p.m.