Triple
T2665980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meirionnydd |
E55635
|
entity |
| Predicate | historicCountyCreated |
P19842
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Meirionnydd, historicCountyCreated, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicCountyCreated Context triple: [Meirionnydd, historicCountyCreated, 16th century]
-
A.
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.
-
B.
historicCountyPredecessor
Indicates that one historic county served as a predecessor or earlier form of another historic county in an administrative or territorial succession.
-
C.
hasHistoricCountyStatusSince
chosen
Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
-
D.
historicParliamentaryCounty
Indicates that an entity is (or was) located within, or associated with, a historic parliamentary county as defined for electoral or administrative purposes.
-
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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd96ed2748190a4feae98199b459d |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.