Triple
T32330008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Lathom |
E826023
|
entity |
| Predicate | notableLandholdingsRegion |
P87581
|
FINISHED |
| Object | Lancashire |
E5501
|
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: Lancashire | Statement: [Earl of Lathom, notableLandholdingsRegion, Lancashire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLandholdingsRegion Context triple: [Earl of Lathom, notableLandholdingsRegion, Lancashire]
-
A.
landholdings
Indicates the extent or collection of land owned, controlled, or held by an entity.
-
B.
landedEstatesRegion
chosen
Indicates that an entity’s landed estates are located within or associated with a particular geographic region.
-
C.
notableLordship
Indicates that an entity holds or has held a particularly significant or distinguished lordship over another entity or domain.
-
D.
notableRegionOfSettlement
Indicates that a specified region is a significant or prominent place where an entity is or has been settled.
-
E.
hasLandholdingsIn
Indicates that an entity owns or controls land or property located within a specified geographic area.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a33e89b9a4c8190a65e3ac7e74296f7 |
completed | June 18, 2026, 12:46 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:47 a.m.