Triple
T24727497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Hall, Southwark |
E618192
|
entity |
| Predicate | servedAsSeatUntil |
P118471
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [City Hall, Southwark, servedAsSeatUntil, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsSeatUntil Context triple: [City Hall, Southwark, servedAsSeatUntil, 2021]
-
A.
hasFormerSeat
chosen
Indicates that an entity previously held a particular seat, position, or place but no longer does so.
-
B.
permanentSeat
Indicates that an entity holds a seat or position that is intended to be ongoing and not subject to regular expiration, rotation, or reappointment.
-
C.
laterSeat
Indicates that one entity is seated in a position that comes after another entity in a specified ordering or sequence of seats.
-
D.
laterHeldSeatIn
Indicates that an individual subsequently occupied or served in a particular seat, position, or office at a later time than some referenced point or role.
-
E.
seatSince
Indicates that an entity has held a particular seat, position, or place continuously since 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 4 a.m.