Triple
T9478534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disputes Tribunal of New Zealand |
E228574
|
entity |
| Predicate | usesLawyers |
P8814
|
FINISHED |
| Object | not usually |
—
|
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: not usually | Statement: [Disputes Tribunal of New Zealand, usesLawyers, not usually]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLawyers Context triple: [Disputes Tribunal of New Zealand, usesLawyers, not usually]
-
A.
legalCodeFocus
Indicates that something is specifically concerned with, centered on, or primarily addressing a particular legal code or body of law.
-
B.
legalRepresentation
chosen
Indicates that one entity formally acts on behalf of another in legal matters, such as providing counsel, advocacy, or defense within a legal system.
-
C.
legalMatters
Indicates that one entity is involved with, concerned about, or responsible for legal issues, processes, or obligations related to another entity or context.
-
D.
legalTool
Indicates a relationship where something functions as a legal instrument, mechanism, or means used to achieve or regulate a legal purpose or outcome.
-
E.
numberOfLawyers
Indicates the quantity of lawyers associated with a given entity or situation.
- 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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd8014fd0c819093bd15816f3db357 |
completed | April 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69cca561e6b0819090aa795f3c3a2083 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:54 p.m.