Triple
T3617381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardiff Council |
E76634
|
entity |
| Predicate | foundedAsUnitaryAuthority |
P49152
|
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: [Cardiff Council, foundedAsUnitaryAuthority, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsUnitaryAuthority Context triple: [Cardiff Council, foundedAsUnitaryAuthority, 1996]
-
A.
isUnitaryAuthority
Indicates that an entity functions as a single-tier local government body with full administrative authority over its area, without sharing powers with a higher or lower local authority.
-
B.
unitaryAuthoritySince
chosen
Indicates the point in time from which an entity has held the status or role of a unitary authority.
-
C.
foundedAsCounty
Indicates that an administrative region or jurisdiction was originally established with the legal status and designation of a county.
-
D.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
-
E.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc27dd030819083d34fee0c06612a |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.