Triple
T25035800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title 23 NYCRR Part 500 |
E626973
|
entity |
| Predicate | complianceDate |
P158711
|
FINISHED |
| Object | 2018-03-01 |
—
|
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: 2018-03-01 | Statement: [Title 23 NYCRR Part 500, complianceDate, 2018-03-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complianceDate Context triple: [Title 23 NYCRR Part 500, complianceDate, 2018-03-01]
-
A.
complianceDateForMostCoveredEntities
Indicates the date by which the majority of entities subject to a given rule or requirement must achieve compliance.
-
B.
certificationDate
Indicates the date on which an entity was officially certified or granted a formal certification.
-
C.
complianceDateForSmallHealthPlans
Indicates the date on which small health plans are required to achieve or demonstrate compliance with a specified rule, standard, or regulation.
-
D.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
-
E.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f47b7f657c81908174590c811a3cbf |
completed | May 1, 2026, 10:07 a.m. |
Created at: April 18, 2026, 6:08 a.m.