Triple
T1589702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Sheriff of Lancashire |
E34149
|
entity |
| Predicate | hasList |
P20315
|
FINISHED |
| Object | list of High Sheriffs of Lancashire by year |
—
|
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: list of High Sheriffs of Lancashire by year | Statement: [High Sheriff of Lancashire, hasList, list of High Sheriffs of Lancashire by year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasList Context triple: [High Sheriff of Lancashire, hasList, list of High Sheriffs of Lancashire by year]
-
A.
isListOf
Indicates that one entity is a collection or sequence whose elements are instances or members of another specified entity.
-
B.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
C.
hasAnnualList
chosen
Indicates that an entity maintains or is associated with a list that is updated or issued on an annual basis.
-
D.
hasListOfMembers
Indicates that an entity is associated with a collection containing its members or constituents.
-
E.
hasListingAuthority
Indicates that an entity has the official power or permission to create, approve, or manage listings for another entity or resource.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93aedd45c819085843ac843d640e8 |
completed | March 5, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69a907bdc19081908c84c5c0aa09e282 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.