Triple
T31779828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Māori Appellate Court |
E811168
|
entity |
| Predicate | canGiveDirectionsTo |
P33699
|
FINISHED |
| Object | Māori Land Court |
—
|
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: Māori Land Court | Statement: [Māori Appellate Court, canGiveDirectionsTo, Māori Land Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canGiveDirectionsTo Context triple: [Māori Appellate Court, canGiveDirectionsTo, Māori Land Court]
-
A.
canProvideDirections
chosen
Indicates that one entity is able to give another entity guidance or instructions on how to reach a particular location or navigate a route.
-
B.
locationDirection
Indicates that one entity is located in a specific directional relation (such as north, south, above, or below) relative to another entity.
-
C.
routeDirectionB
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
-
D.
nearbyTransit
Indicates that one location has public transportation options situated within a short distance or easy access from it.
-
E.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
- 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.