Triple
T32413319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act of Parliament of Pakistan |
E828280
|
entity |
| Predicate | comesIntoForceBy |
P174052
|
FINISHED |
| Object | commencement provision |
—
|
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: commencement provision | Statement: [Act of Parliament of Pakistan, comesIntoForceBy, commencement provision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comesIntoForceBy Context triple: [Act of Parliament of Pakistan, comesIntoForceBy, commencement provision]
-
A.
cameIntoForceBefore
Indicates that one legal instrument, rule, or agreement became legally effective earlier in time than another.
-
B.
cameIntoForceInYear
Indicates that a law, agreement, or formal measure became legally effective or operational in a specified calendar year.
-
C.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
D.
dateEnacted
Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
-
E.
charterEnteredIntoForce
Indicates that a charter has become legally effective and binding as of a specific point in time.
- F. None of above. chosen
Provenance (4 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c25a81208190b108ab80ca851ff9 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:53 a.m.