Triple
T10823478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lee, London |
E255433
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Grove Park, London |
E221607
|
NE 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: Grove Park, London | Statement: [Lee, London, adjacentTo, Grove Park, London]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Grove Park, London Context triple: [Lee, London, adjacentTo, Grove Park, London]
-
A.
Grove Park
Grove Park is a public recreational park located in the city of Wyoming, Ohio.
-
B.
Grove Park
chosen
Grove Park is a suburban area in southeast London, England, known for its residential character and rail links into central London.
-
C.
Grove Park, Carshalton
Grove Park, Carshalton is a historic riverside public park in the London Borough of Sutton, known for its landscaped gardens, ornamental features, and access to the River Wandle.
-
D.
Green Park
Green Park is a public park in Kanpur, India, historically significant enough to lend its name to the nearby Green Park Stadium.
-
E.
Green Park
Green Park is a central London royal park known for its open lawns, mature trees, and tranquil atmosphere between Buckingham Palace and Piccadilly.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7344c551c8190a7491d468b8a4a04 |
completed | April 9, 2026, 5:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e344249f648190b541c7fad7a834f5 |
completed | April 18, 2026, 8:43 a.m. |
Created at: April 8, 2026, 9:19 p.m.