Triple
T18018181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple Bar |
E431046
|
entity |
| Predicate | returnedToCityOfLondon |
P129436
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Temple Bar, returnedToCityOfLondon, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToCityOfLondon Context triple: [Temple Bar, returnedToCityOfLondon, 2004]
-
A.
returnedToEngland
Indicates that an entity went back to England after having been away.
-
B.
governingCityAfterReturn
Indicates that a city serves as the governing or administrative center for an entity after that entity has returned from a prior location or state.
-
C.
returnedVia
Indicates that something was sent back or responded to through a specified medium, channel, or method.
-
D.
returnedToIsleOfManTT
Indicates that an entity resumed participation in, or attendance at, the Isle of Man TT event after having been away or absent.
-
E.
secondaryLondonTerminal
Indicates that a location serves as a secondary terminal in London associated with a primary London terminal for a given service or route.
- F. None of above. chosen
Provenance (4 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9bf85c08190a40cef4c6d7b566a |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:24 a.m.