Triple
T30966581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ceremonial county of Dyfed |
E788973
|
entity |
| Predicate | hasHistoricCountyPrecursor |
P195973
|
FINISHED |
| Object | Dyfed |
—
|
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: Dyfed | Statement: [ceremonial county of Dyfed, hasHistoricCountyPrecursor, Dyfed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricCountyPrecursor Context triple: [ceremonial county of Dyfed, hasHistoricCountyPrecursor, Dyfed]
-
A.
historicCountyPredecessor
Indicates that one historic county served as a predecessor or earlier form of another historic county in an administrative or territorial succession.
-
B.
hasAssociatedHistoricCounty
Indicates that an entity is linked to a specific historic county with which it is geographically or administratively associated.
-
C.
hasHistoricCountyStatusSince
Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
-
D.
hasHistoricCountyCore
Indicates that an entity is fundamentally based in, derived from, or primarily associated with a particular historic county as its core area.
-
E.
hasHistoricCountyCode
Indicates that an entity is associated with a specific historic county, identified by its county code.
- F. None of above. chosen
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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
| PDg | Predicate description generation | batch_69fdfbae00e481908a2e4558b9dee07e |
completed | May 8, 2026, 3:05 p.m. |
Created at: April 29, 2026, 8:54 p.m.