Triple
T26864294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey Open Public Meetings Act |
E676421
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New Jersey state statute |
C4528
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: New Jersey state statute Context triple: [New Jersey Open Public Meetings Act, instanceOf, New Jersey state statute]
-
A.
New Jersey legislative district
A New Jersey legislative district is a geographically defined area within the state from which residents elect one state senator and two General Assembly members to the New Jersey Legislature.
-
B.
New York State program
A New York State program is an organized, state-administered initiative designed to deliver specific public services, benefits, or regulatory functions to residents, businesses, or communities within New York State.
-
C.
New York State government document
A New York State government document is an official record, publication, or communication produced or issued by an agency, department, or office of the New York State government in the course of its public duties.
-
D.
United States state law
chosen
United States state law is the body of legal rules, regulations, and judicial decisions enacted and applied by an individual U.S. state to govern conduct, resolve disputes, and organize governmental powers within its jurisdiction.
-
E.
county of New Jersey
A county of New Jersey is a primary local government and administrative subdivision of the state, encompassing multiple municipalities and providing regional services such as law enforcement, courts, and infrastructure management.
- F. None of above.
Provenance (1 batch)
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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:27 a.m.