Triple
T24727496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Hall, Southwark |
E618192
|
entity |
| Predicate | servedAsSeatFrom |
P80688
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [City Hall, Southwark, servedAsSeatFrom, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsSeatFrom Context triple: [City Hall, Southwark, servedAsSeatFrom, 2002]
-
A.
hasSeatAt
Indicates that an entity occupies or holds a place, position, or membership within a specific group, body, or location.
-
B.
hasHistoricalSeat
Indicates that an entity possesses or is associated with a historically significant seat, location, or place of authority.
-
C.
seatSince
chosen
Indicates that an entity has held a particular seat, position, or place continuously since a specified point in time.
-
D.
notableSeat
Indicates that an entity holds or is associated with a seat, position, or place that is considered notable or significant in some context.
-
E.
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.
- 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_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 4 a.m.