Triple
T17272675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumberland, England |
E419302
|
entity |
| Predicate | historicCountyCodeChapman |
P57420
|
FINISHED |
| Object | CUL |
—
|
LITERAL 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: CUL | Statement: [Cumberland, England, historicCountyCodeChapman, CUL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicCountyCodeChapman Context triple: [Cumberland, England, historicCountyCodeChapman, CUL]
-
A.
historicCountyPart
Indicates that one entity forms a constituent part or subdivision of a historic county.
-
B.
historicalCounty
Indicates that an entity was located within or associated with a county as it existed in the past, even if that county’s boundaries or administrative status have since changed.
-
C.
hasHistoricCountyCode
chosen
Indicates that an entity is associated with a specific historic county, identified by its county code.
-
D.
hasHistoricCountyNumber
Indicates that an entity is associated with a specific identifier corresponding to its historic county designation.
-
E.
historicCountyPredecessor
Indicates that one historic county served as a predecessor or earlier form of another historic county in an administrative or territorial succession.
- F. None of above.
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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4b023c8190b92df4015c14c3a8 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.