Triple
T27249745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earls of Derby |
E687451
|
entity |
| Predicate | historicalSeatRegion |
P13711
|
FINISHED |
| Object | Lancashire |
—
|
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: Lancashire | Statement: [Earls of Derby, historicalSeatRegion, Lancashire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalSeatRegion Context triple: [Earls of Derby, historicalSeatRegion, Lancashire]
-
A.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
B.
historicalRegionCode
Indicates that an entity is associated with a specific code identifying a historical region.
-
C.
historicalRegionCorrespondsTo
Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
-
D.
historicalAdministrativeRegionName
Indicates the name assigned to an administrative region as it existed during a specific historical period.
-
E.
historicalRegionAssociation
chosen
Indicates an association where an entity is or was located in, part of, or otherwise related to a specific historical region.
- 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_69ef35567e808190a94458cd44ebff0c |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 27, 2026, 10:44 a.m.