Triple
T5506559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fulham |
E144453
|
entity |
| Predicate | hasPark |
P105
|
FINISHED |
| Object | Eel Brook Common |
E464194
|
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: Eel Brook Common | Statement: [Fulham, hasPark, Eel Brook Common]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eel Brook Common Context triple: [Fulham, hasPark, Eel Brook Common]
-
A.
Eel Brook Common
chosen
Eel Brook Common is a public green space in Fulham, London, known for its open lawns, sports facilities, and community events.
-
B.
Ashtead Common
Ashtead Common is a large ancient woodland and nature reserve in Surrey, England, known for its veteran oak trees and rich biodiversity.
-
C.
Cimla Common
Cimla Common is a public open green space in Cimla, Neath, used for recreation and community activities.
-
D.
Hungerford Common
Hungerford Common is a large open area of common land near the town of Hungerford in Berkshire, England, known for its grazing, walking paths, and wildlife.
-
E.
Hayes Common
Hayes Common is a large area of heathland and woodland in the London Borough of Bromley, valued for recreation and nature conservation.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f47d2dc8190ad874be6902d8a4c |
completed | March 22, 2026, 4:56 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c027b7ef2481908b43f34721b8a8b3 |
completed | March 22, 2026, 5:32 p.m. |
Created at: March 22, 2026, 3:32 p.m.