Triple
T13191901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radnorshire |
E314010
|
entity |
| Predicate | absorbedIntoOnDate |
P107547
|
FINISHED |
| Object | 1974-04-01 |
—
|
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: 1974-04-01 | Statement: [Radnorshire, absorbedIntoOnDate, 1974-04-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: absorbedIntoOnDate Context triple: [Radnorshire, absorbedIntoOnDate, 1974-04-01]
-
A.
dateAbsorbed
chosen
Indicates that one entity was absorbed or incorporated into another entity on a specific date.
-
B.
incorporatedIntoOnDate
Indicates that one entity was formally incorporated into or merged with another entity on a specific date.
-
C.
dateAbsorbedApprox
Indicates that one entity was absorbed into another on an approximate or uncertain date, rather than on a precisely known date.
-
D.
admittedSuccessorEntityDate
Indicates the date on which a successor entity was formally admitted or recognized as taking over from a predecessor.
-
E.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:15 p.m.