Triple
T36580874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capel Celyn |
E902390
|
entity |
| Predicate | administrativeAreaAtTime |
P196679
|
FINISHED |
| Object | Merionethshire |
—
|
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: Merionethshire | Statement: [Capel Celyn, administrativeAreaAtTime, Merionethshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeAreaAtTime Context triple: [Capel Celyn, administrativeAreaAtTime, Merionethshire]
-
A.
hasAdministrativeArea
Indicates that one entity serves as the governing or jurisdictional area responsible for administering another entity.
-
B.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
C.
laterAdministrativeRegion
Indicates that an entity became part of, or was replaced by, another administrative region at a later point in time.
-
D.
associatedAdministrativeRegion
Indicates that an entity is linked to, or falls under the jurisdiction of, a particular administrative region.
-
E.
denotesAdministrativeArea
Indicates that one entity designates or specifies another entity as its relevant administrative area or jurisdiction.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69fe610d75a48190bfd08a9bb957fcd3 |
completed | May 8, 2026, 10:17 p.m. |
Created at: May 3, 2026, 4:11 p.m.