Triple
T2465575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clwyd |
E55238
|
entity |
| Predicate | statusAfter1996 |
P40012
|
FINISHED |
| Object | preserved county for ceremonial purposes |
—
|
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: preserved county for ceremonial purposes | Statement: [Clwyd, statusAfter1996, preserved county for ceremonial purposes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfter1996 Context triple: [Clwyd, statusAfter1996, preserved county for ceremonial purposes]
-
A.
statusAfter1956
Indicates the status or condition of an entity as it existed at any time after the year 1956.
-
B.
statusAfter1934
Indicates the condition or state something has specifically after the year 1934.
-
C.
statusAfter2010
Indicates the condition or state of an entity specifically in the period after the year 2010.
-
D.
legalStatusAfter2009
Indicates the legal status or condition that an entity holds from the year 2009 onward, typically reflecting changes due to laws or regulations taking effect at or after that time.
-
E.
legalStatusAfter1983
Indicates the legal status or classification that an entity holds starting from the year 1983 onward.
- 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_69ab49e3622c8190ad22afa2c4fbb807 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0b3ea308190a6d8499c2a542c50 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd2baee308190bdaa41ef1f6bc9cc |
completed | March 7, 2026, 7:24 a.m. |
Created at: March 6, 2026, 9:44 p.m.