Triple
T2013097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceredigion |
E43732
|
entity |
| Predicate | createdAsPrincipalArea |
P18356
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Ceredigion, createdAsPrincipalArea, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdAsPrincipalArea Context triple: [Ceredigion, createdAsPrincipalArea, 1996]
-
A.
createdUnderAdministrationOf
Indicates that something was created during the period when a particular person, group, or authority was in charge or held administrative control.
-
B.
createdAs
Indicates that one entity was originally made, designed, or brought into existence in the form, role, or identity specified by another entity.
-
C.
createdForJurisdiction
chosen
Indicates that something was created specifically to apply within, serve, or be used by a particular legal or geographic jurisdiction.
-
D.
createdAgencyWithin
Indicates that one entity established or formed an agency or organizational unit within the scope, structure, or authority of another entity.
-
E.
primaryArea
Indicates that one entity is the main or most important area, domain, or field associated with another entity.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b42d508190bf2b63132bb2ad77 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.