Triple
T4081879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trade Disputes and Trade Unions Act 1927 |
E87493
|
entity |
| Predicate | repealedIn |
P6257
|
FINISHED |
| Object | 1946 |
—
|
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: 1946 | Statement: [Trade Disputes and Trade Unions Act 1927, repealedIn, 1946]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repealedIn Context triple: [Trade Disputes and Trade Unions Act 1927, repealedIn, 1946]
-
A.
repealed
chosen
Indicates that a law, rule, or regulation has been officially revoked or annulled so that it no longer has legal effect.
-
B.
repealedProvisionOf
Indicates that one legal provision has been formally revoked, annulled, or rendered no longer in force by another provision or act.
-
C.
abolishedInEffectBy
Indicates that the legal force or practical operation of something is nullified or terminated as a result of another specified action or measure.
-
D.
repealProcess
Indicates the process by which an existing law, rule, or regulation is formally revoked or annulled.
-
E.
abolishedDuring
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by another 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc77dab481909bcf197daf2def59 |
completed | March 9, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.