Triple
T37998399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Katharine’s by the Tower, London |
E948023
|
entity |
| Predicate | successorLaterLocation |
P42649
|
FINISHED |
| Object | Limehouse |
—
|
NE NERFINISHED |
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: Limehouse | Statement: [St Katharine’s by the Tower, London, successorLaterLocation, Limehouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorLaterLocation Context triple: [St Katharine’s by the Tower, London, successorLaterLocation, Limehouse]
-
A.
successorLocation
Indicates that one location directly follows or comes after another in a defined spatial or ordered sequence.
-
B.
successorStateLocation
Indicates that one location represents the state or position that directly follows another location in a defined sequence or process.
-
C.
successorEventLocation
Indicates that the location is where the immediately following or next event in a sequence takes place.
-
D.
laterLocation
chosen
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
E.
successorFacilityLocation
Indicates that one facility location directly follows or replaces another in a sequence or succession of locations.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00c59b03dc8190870f0dd24603a1ef |
completed | May 10, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a00c5178bc88190b2a0e03f38314035 |
completed | May 10, 2026, 5:49 p.m. |
Created at: May 3, 2026, 4:20 p.m.