Triple
T27238981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebergham |
E687148
|
entity |
| Predicate | shireCountyHistoric |
P4770
|
FINISHED |
| Object | Cumberland |
E1634443
|
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: Cumberland | Statement: [Sebergham, shireCountyHistoric, Cumberland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shireCountyHistoric Context triple: [Sebergham, shireCountyHistoric, Cumberland]
-
A.
coversHistoricCounty
Indicates that one entity geographically encompasses the area of a historic county.
-
B.
shireCounty
chosen
Indicates the county-level administrative area (shire county) within which a given place or entity is located or governed.
-
C.
historicCountyPart
Indicates that one entity forms a constituent part or subdivision of a historic county.
-
D.
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.
-
E.
historicParliamentaryCounty
Indicates that an entity is (or was) located within, or associated with, a historic parliamentary county as defined for electoral or administrative purposes.
- F. None of above.
Provenance (4 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6267c112c8190986426190320e1ac |
completed | May 2, 2026, 4:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1262773dac8190bb4113ab4e9b3f82 |
completed | May 24, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 10:36 a.m.