Triple
T5130694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cynon Valley |
E115689
|
entity |
| Predicate | localGovernmentDistrictExistedUntil |
P3903
|
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: [Cynon Valley, localGovernmentDistrictExistedUntil, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localGovernmentDistrictExistedUntil Context triple: [Cynon Valley, localGovernmentDistrictExistedUntil, 1996]
-
A.
existedAsCountyUntil
Indicates that an entity functioned with the status or designation of a county up to a specified end date or time period.
-
B.
unitaryAuthoritySince
Indicates the point in time from which an entity has held the status or role of a unitary authority.
-
C.
historicCountyAbolishedAsAdministrativeUnit
Indicates that a historic county ceased to function as an official administrative unit.
-
D.
dissolvedOrAbolished
Indicates that an organization, institution, or formal entity has been officially terminated, disbanded, or ceased to exist.
-
E.
dateAbolished
chosen
Indicates the date on which something (such as an institution, law, practice, or position) was officially ended or abolished.
- 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_69bd444426bc819099ccd23f141e22aa |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7fef2e8c8190982dd67f50295ada |
completed | March 20, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69bd77ac2fc48190abeebb003a82384c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:42 p.m.