Triple
T27238982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebergham |
E687148
|
entity |
| Predicate | districtHistoric |
P295
|
FINISHED |
| Object | Allerdale |
—
|
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: Allerdale | Statement: [Sebergham, districtHistoric, Allerdale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: districtHistoric Context triple: [Sebergham, districtHistoric, Allerdale]
-
A.
isHistoricDistrict
Indicates that an area has been officially recognized or designated as a historic district due to its historical, cultural, or architectural significance.
-
B.
hasHistoricDistrict
chosen
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
-
C.
primaryLocationHistoric
Indicates the historically primary or most significant location associated with an entity, such as where it was originally based, founded, or chiefly active in the past.
-
D.
historicalSociety
Indicates that an entity is a society or organization dedicated to preserving, studying, or promoting history.
-
E.
sharesHistoricDistrictWith
Indicates that two entities are located within or associated with the same designated historic district.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 10:36 a.m.