Triple
T20992935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumberland (historic county) |
E517069
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Longtown |
—
|
NE NERFINISHED |
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: Longtown | Statement: [Cumberland (historic county), contains, Longtown]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Longtown Context triple: [Cumberland (historic county), contains, Longtown]
-
A.
Longtown
chosen
Longtown is a small town in Cumbria, England, situated near the Scottish border and historically associated with the county of Cumberland.
-
B.
Tylorstown
Tylorstown is a former coal mining village in the Rhondda Fach valley in Rhondda Cynon Taf, Wales.
-
C.
Rocktown
Rocktown was the original name of what is now Harrisonburg, Virginia, a city in the Shenandoah Valley.
-
D.
Dutchtown
Dutchtown is a small village located in Cape Girardeau County in southeastern Missouri, United States.
-
E.
Woodston
Woodston is a residential and industrial suburb of Peterborough in Cambridgeshire, England, situated just south of the city centre by the River Nene.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc1d829081908de889c542734393 |
completed | April 21, 2026, 4:25 a.m. |
Created at: April 16, 2026, 1:50 p.m.