Triple
T16298301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brockley |
E395708
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Ladywell |
E315466
|
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: Ladywell | Statement: [Brockley, adjacentTo, Ladywell]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ladywell Context triple: [Brockley, adjacentTo, Ladywell]
-
A.
Ladywell
Ladywell is a residential neighbourhood within the town of Livingston in West Lothian, Scotland.
-
B.
Ladywell
chosen
Ladywell is a residential district in the London Borough of Lewisham, known for its local high street, green spaces, and commuter rail links into central London.
-
C.
Saltwell
Saltwell is a British Labour Party politician who served as the Member of Parliament for Newcastle upon Tyne West in the early 20th century.
-
D.
Saltwell
Saltwell is a low-power Intel microarchitecture designed primarily for energy-efficient Atom processors used in mobile and embedded devices.
-
E.
Backwell
Backwell is a village and civil parish in North Somerset, England, known for its commuter links to Bristol and its mix of rural and suburban character.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e2f486c8190b73c15f59335cde2 |
completed | April 17, 2026, 4:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a001f9d7ef48190b7acebebcb9608c3 |
completed | May 10, 2026, 6:03 a.m. |
Created at: April 10, 2026, 5:06 a.m.