Triple
T5665635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand law |
E124849
|
entity |
| Predicate | hasLegalSystemType |
P65627
|
FINISHED |
| Object | unitary state |
—
|
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: unitary state | Statement: [New Zealand law, hasLegalSystemType, unitary state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalSystemType Context triple: [New Zealand law, hasLegalSystemType, unitary state]
-
A.
partOfLegalSystem
Indicates that something belongs to, is included within, or functions as a component of a particular legal system.
-
B.
hasTypeOfCourt
Indicates that an entity is associated with or classified by a specific type or category of court.
-
C.
legalSystemFeature
Indicates a characteristic, rule, or structural element that forms part of a particular legal system.
-
D.
governedByLegalRegime
Indicates that an entity is subject to, regulated by, or operating under a specific legal framework or set of legal rules.
-
E.
relatedLegalSystem
Indicates that there is an association or connection between two legal systems, such as influence, similarity, shared origin, or mutual relevance.
- 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c0236af5308190b3d698eadf7bcd2b |
completed | March 22, 2026, 5:14 p.m. |
Created at: March 22, 2026, 3:43 p.m.