Triple
T10665420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bucklebury |
E251343
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Reading |
E22663
|
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: Reading | Statement: [Bucklebury, locatedNear, Reading]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Reading Context triple: [Bucklebury, locatedNear, Reading]
-
A.
Reading
"Reading" is an Impressionist painting by Berthe Morisot that depicts a quiet, intimate moment of a woman absorbed in a book.
-
B.
Reading
chosen
Reading is a major town in Berkshire, England, known as a key commercial and transport hub in the Thames Valley.
-
C.
Reading
Reading is a historic city in southeastern Pennsylvania known for its industrial heritage, transportation links, and role as a regional cultural and economic center.
-
D.
Read
Read is a village in Lancashire, England, situated near the River Calder and known for its residential community and local amenities.
-
E.
Read
Read is a surname shared by various notable individuals across fields such as politics, arts, and academia.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6f31f87748190bb44db8afa901763 |
completed | April 9, 2026, 12:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d9885dc17881909df20abedd9da5e3 |
completed | April 10, 2026, 11:31 p.m. |
Created at: April 8, 2026, 9:08 p.m.