Triple
T31779821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Māori Appellate Court |
E811168
|
entity |
| Predicate | canStateCaseFor |
P163207
|
FINISHED |
| Object | High Court of New Zealand |
—
|
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: High Court of New Zealand | Statement: [Māori Appellate Court, canStateCaseFor, High Court of New Zealand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canStateCaseFor Context triple: [Māori Appellate Court, canStateCaseFor, High Court of New Zealand]
-
A.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
-
B.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
C.
canMake
Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
-
D.
canDeclare
Indicates that one entity has the authority or ability to formally declare or announce something about another entity or situation.
-
E.
canSubmitCasesTo
chosen
Indicates that one entity has the permission or capability to submit cases to 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe3df6c8190ac4fb42c2a2034c9 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:36 p.m.