Triple
T24727104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seisyllwg |
E618182
|
entity |
| Predicate | includesHistoricRegion |
P97330
|
FINISHED |
| Object | Ceredigion |
—
|
NE NERFINISHED |
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: Ceredigion | Statement: [Seisyllwg, includesHistoricRegion, Ceredigion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesHistoricRegion Context triple: [Seisyllwg, includesHistoricRegion, Ceredigion]
-
A.
isHistoricRegionFor
Indicates that one entity serves as a historically recognized region associated with, or significant to, another entity.
-
B.
historicallyIncludedRegion
chosen
Indicates that one region was formerly part of, or contained within, another region during a past historical period.
-
C.
isInHistoricRegion
Indicates that an entity is located within or belongs to a historically recognized geographic region.
-
D.
historicalRegionCorrespondsTo
Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
-
E.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 18, 2026, 4 a.m.