Triple
T419557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation A |
E8069
|
entity |
| Predicate | effectiveDateOfMajorAmendments |
P11741
|
FINISHED |
| Object | June 2015 |
—
|
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: June 2015 | Statement: [Regulation A, effectiveDateOfMajorAmendments, June 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveDateOfMajorAmendments Context triple: [Regulation A, effectiveDateOfMajorAmendments, June 2015]
-
A.
majorAmendmentDate
chosen
Indicates the date on which a significant change or revision to something was formally made or took effect.
-
B.
hasAmendments
Indicates that one entity (such as a document, law, or agreement) includes or is associated with one or more modifications, changes, or additions made after its original creation.
-
C.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
D.
updatedSpecificationDate
Indicates the date on which a specification was last revised or brought up to date.
-
E.
amendedBy
Indicates that one entity has been modified, revised, or updated as a result of changes made 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd3b948819097d96c73d0a0f699 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.