Triple
T38002613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radnorshire |
E948144
|
entity |
| Predicate | historicCountyCreatedBy |
P203754
|
FINISHED |
| Object | Laws in Wales Acts |
E233875
|
NE 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: Laws in Wales Acts | Statement: [Radnorshire, historicCountyCreatedBy, Laws in Wales Acts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicCountyCreatedBy Context triple: [Radnorshire, historicCountyCreatedBy, Laws in Wales Acts]
-
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.
historicCountyPart
Indicates that one entity forms a constituent part or subdivision of a historic county.
-
C.
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.
-
D.
hasHistoricCountyStatusSince
Indicates that an entity has held the legal or recognized status of a historic county starting from a specified point in time.
-
E.
hasHistoricCountyCode
Indicates that an entity is associated with a specific historic county, identified by its county code.
- F. None of above. chosen
Provenance (5 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_6a01e3a2d0e08190a7d5622920dc56e6 |
completed | May 11, 2026, 2:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a412cc536f481909dfd7610d64086a3 |
completed | June 28, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_6a01e3013e7881909f0cdca25a53c009 |
completed | May 11, 2026, 2:09 p.m. |
| PDg | Predicate description generation | batch_6a01e3a226948190b9c0e693a6a5e4c1 |
completed | May 11, 2026, 2:11 p.m. |
Created at: May 3, 2026, 4:20 p.m.