Triple
T3031965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gramm-Leach-Bliley Act of 1999 |
E82916
|
entity |
| Predicate | dateSignedIntoLaw |
P45102
|
FINISHED |
| Object | 1999-11-12 |
—
|
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: 1999-11-12 | Statement: [Gramm-Leach-Bliley Act of 1999, dateSignedIntoLaw, 1999-11-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateSignedIntoLaw Context triple: [Gramm-Leach-Bliley Act of 1999, dateSignedIntoLaw, 1999-11-12]
-
A.
signedIntoLawIn
Indicates that a proposed law or bill was formally approved and enacted by an authorized official in a specific place or jurisdiction.
-
B.
legislatedOn
Indicates that a legislative body has formally considered, debated, or enacted laws or regulations concerning a particular subject or entity.
-
C.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
D.
dateOfPromulgation
Indicates the date on which a law, decree, or official act is formally proclaimed and put into effect.
-
E.
dateEnacted
Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9aefc2dc8190ad9b349ca45b7e30 |
completed | March 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 3:01 p.m.