Triple
T14033881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlton House |
E337659
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Charlton |
E236068
|
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: Charlton | Statement: [Charlton House, locatedIn, Charlton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Charlton Context triple: [Charlton House, locatedIn, Charlton]
-
A.
Charlton
Charlton is a small town in upstate New York known for its rural character and residential communities.
-
B.
Charlton
chosen
Charlton is a district in southeast London known for its historic village center, riverside industrial heritage, and the football club Charlton Athletic.
-
C.
Charlton
Charlton is a small settlement located within the borough of Spelthorne in Surrey, England.
-
D.
Charltons
Charltons is a small village in North Yorkshire, England, situated within the borough of Redcar and Cleveland.
-
E.
Charfield
Charfield is a rural village and civil parish in South Gloucestershire, England, known historically for its former railway station and the 1928 Charfield rail disaster.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fac71188190a586049405f1071e |
completed | April 14, 2026, 12:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbc337a5cc8190953b84255a401ada |
completed | May 6, 2026, 10:39 p.m. |
Created at: April 9, 2026, 10:20 p.m.