Triple
T34416269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statutum Walliae |
E883409
|
entity |
| Predicate | createdAdministrativeUnit |
P53540
|
FINISHED |
| Object | county of Anglesey |
—
|
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: county of Anglesey | Statement: [Statutum Walliae, createdAdministrativeUnit, county of Anglesey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdAdministrativeUnit Context triple: [Statutum Walliae, createdAdministrativeUnit, county of Anglesey]
-
A.
createdAsAdministrativeUnit
chosen
Indicates that an entity was brought into existence specifically to function as an administrative unit within an organizational or governmental structure.
-
B.
laterAdministrativeUnit
Indicates that one administrative unit succeeds or replaces another in time, coming into effect at a later date.
-
C.
formerAdministrativeUnitType
Indicates that an entity previously held a specific type or classification of administrative unit, but no longer does so.
-
D.
administrativeUnitType
Indicates the specific kind or category of administrative unit involved in the relationship (e.g., city, county, province).
-
E.
connectsAdministrativeUnits
Indicates a relationship where one administrative unit is linked or associated with another for governance, coordination, or organizational purposes.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: May 1, 2026, 1:59 a.m.