Triple
T35224369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Ceredigion |
E1017048
|
entity |
| Predicate | historicalCountyCoreOf |
P115529
|
FINISHED |
| Object | Cardiganshire |
—
|
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: Cardiganshire | Statement: [Kingdom of Ceredigion, historicalCountyCoreOf, Cardiganshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalCountyCoreOf Context triple: [Kingdom of Ceredigion, historicalCountyCoreOf, Cardiganshire]
-
A.
hasHistoricCountyCore
chosen
Indicates that an entity is fundamentally based in, derived from, or primarily associated with a particular historic county as its core area.
-
B.
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.
-
C.
historicCountyPart
Indicates that one entity forms a constituent part or subdivision of a historic county.
-
D.
hasAssociatedHistoricCounty
Indicates that an entity is linked to a specific historic county with which it is geographically or administratively associated.
-
E.
hasHistoricCountyCode
Indicates that an entity is associated with a specific historic county, identified by its county code.
- 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00a74c0564819081e1c4c29b9d0d15 |
completed | May 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_6a00a6a63ef48190a743c88534d9d672 |
completed | May 10, 2026, 3:39 p.m. |
Created at: May 3, 2026, 4:02 p.m.