Triple
T11647360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British nationality law |
E276809
|
entity |
| Predicate | cameIntoMajorEffect |
P49366
|
FINISHED |
| Object | 1 January 1983 |
—
|
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: 1 January 1983 | Statement: [British nationality law, cameIntoMajorEffect, 1 January 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameIntoMajorEffect Context triple: [British nationality law, cameIntoMajorEffect, 1 January 1983]
-
A.
majorImpact
Indicates that one entity has a significant, highly influential, or transformative effect on another entity or outcome.
-
B.
tookEffect
chosen
Indicates that a change, rule, condition, or event became active, operative, or started producing its intended consequences.
-
C.
impactWhenIntroduced
Indicates the effect or consequence that occurs at the moment something is first introduced or brought into a context.
-
D.
cameToPowerThrough
Indicates the manner or process by which an entity attained authority, leadership, or control, specifying how it rose to power.
-
E.
cameIntoEffectInDecade
Indicates that something (such as a law, policy, or agreement) officially began to be in force during a specified decade.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cd9bb0819093d107204bed2fe0 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.