Triple
T17764204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electoral Act 1956 |
E443460
|
entity |
| Predicate | wasInForceUntil |
P32336
|
FINISHED |
| Object | Electoral Act 1993 came into force |
—
|
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: Electoral Act 1993 came into force | Statement: [Electoral Act 1956, wasInForceUntil, Electoral Act 1993 came into force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasInForceUntil Context triple: [Electoral Act 1956, wasInForceUntil, Electoral Act 1993 came into force]
-
A.
wasInForceDuring
Indicates that a rule, law, agreement, or other normative provision was legally valid and operative throughout a specified time period.
-
B.
cessationDate
Indicates the date on which an ongoing state, activity, or relationship comes to an end.
-
C.
remainedInForceUntil
chosen
Indicates that a rule, condition, or state continued to be valid or effective up to a specified point in time.
-
D.
cameIntoForceBefore
Indicates that one legal instrument, rule, or agreement became legally effective earlier in time than another.
-
E.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fb2a3c81908887d1d36aee942d |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:11 a.m.