Triple
T23518883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Eagle Centre |
E574445
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Derby city centre |
—
|
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: Derby city centre | Statement: [The Eagle Centre, serves, Derby city centre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Derby city centre Context triple: [The Eagle Centre, serves, Derby city centre]
-
A.
Derby city cultural quarter
Derby city cultural quarter is a designated cultural district in Derby, England, known for its concentration of arts venues, theatres, and creative industries.
-
B.
Derby City
Derby City is a popular nickname for Louisville, Kentucky, reflecting the city's fame as home of the Kentucky Derby horse race.
-
C.
Derby
chosen
Derby is a historic city in Derbyshire, England, known for its industrial heritage, particularly in railways and engineering.
-
D.
Derby
Derby is a neighborhood within the Brazilian city of Recife, known for its central location and urban character.
-
E.
Derby
Derby is a surname of English origin associated with notable historical figures such as American merchant Elias Hasket Derby.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa84fe7c8190aa1078a118af7d61 |
completed | April 29, 2026, 6:51 a.m. |
Created at: April 17, 2026, 6:08 p.m.