Triple
T36580878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capel Celyn |
E902390
|
entity |
| Predicate | dateOfParliamentaryAct |
P1124
|
FINISHED |
| Object | 1957 |
—
|
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: 1957 | Statement: [Capel Celyn, dateOfParliamentaryAct, 1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfParliamentaryAct Context triple: [Capel Celyn, dateOfParliamentaryAct, 1957]
-
A.
dateOfRoyalAssent
Indicates the specific date on which a proposed law or bill formally receives royal assent and thereby becomes law.
-
B.
dateOfEnactment
chosen
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
C.
parliamentaryActAssociatedWith
Indicates that there is an association or linkage between an entity and a specific parliamentary act, such as being created, defined, governed, or affected by that legislation.
-
D.
dateOfPromulgation
Indicates the date on which a law, decree, or official act is formally proclaimed and put into effect.
-
E.
legislatedOn
Indicates that a legislative body has formally considered, debated, or enacted laws or regulations concerning a particular subject or 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 3, 2026, 4:11 p.m.