Triple
T25650779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand electoral law |
E643093
|
entity |
| Predicate | hasCoreStatute |
P143872
|
FINISHED |
| Object | Electoral Act 1993 |
—
|
NE NERFINISHED |
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: Electoral Act 1993 | Statement: [New Zealand electoral law, hasCoreStatute, Electoral Act 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreStatute Context triple: [New Zealand electoral law, hasCoreStatute, Electoral Act 1993]
-
A.
hasMainStatute
chosen
Indicates that one legal document, case, or context is primarily governed, defined, or authorized by a specific statute.
-
B.
hasStatutes
Indicates that one entity possesses, is governed by, or is associated with a set of formal laws or statutes defined by another entity.
-
C.
hasStatuteLaw
Indicates that a jurisdiction or entity is governed by, or possesses, a body of formal written laws enacted by a legislative authority.
-
D.
hasMunicipalStatute
Indicates that a municipality is governed or regulated by a specific municipal statute or ordinance.
-
E.
establishedByStatute
Indicates that something has been formally created, defined, or authorized through a specific law or statute.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 21, 2026, 6:22 p.m.