Triple
T26434532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brycheiniog |
E664602
|
entity |
| Predicate | historicalCountyCorrespondence |
P1069
|
FINISHED |
| Object | Brecknockshire |
—
|
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: Brecknockshire | Statement: [Brycheiniog, historicalCountyCorrespondence, Brecknockshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalCountyCorrespondence Context triple: [Brycheiniog, historicalCountyCorrespondence, Brecknockshire]
-
A.
historicalCountyChange
Indicates that a county’s administrative boundaries or status have been altered over time, such as through creation, dissolution, merger, or territorial reassignment.
-
B.
historicalCounty
chosen
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.
hasHistoricCountyCode
Indicates that an entity is associated with a specific historic county, identified by its county code.
-
D.
hasAssociatedHistoricCounty
Indicates that an entity is linked to a specific historic county with which it is geographically or administratively associated.
-
E.
hasHistoricCountyNumber
Indicates that an entity is associated with a specific identifier corresponding to its historic county designation.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 26, 2026, 11:52 p.m.