Triple
T38002614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radnorshire |
E948144
|
entity |
| Predicate | administrativeCountyCreated |
P179501
|
FINISHED |
| Object | 1889 |
—
|
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: 1889 | Statement: [Radnorshire, administrativeCountyCreated, 1889]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeCountyCreated Context triple: [Radnorshire, administrativeCountyCreated, 1889]
-
A.
hasCountyAdministration
Indicates that an entity is governed, managed, or served by a specific county-level administrative authority.
-
B.
establishedAsCountyInCurrentForm
chosen
Indicates that an administrative region became a county in its present organizational or territorial form on a specific date or during a specific period.
-
C.
unitaryAuthoritySince
Indicates the point in time from which an entity has held the status or role of a unitary authority.
-
D.
hasModernAdministrativeCounty
Indicates that an entity is located within or associated with a specific modern administrative county as defined by current governmental boundaries.
-
E.
ceremonialCountyCreated
Indicates that a ceremonial county was formally established or brought into existence.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: May 3, 2026, 4:20 p.m.