Triple
T24832083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waiwai |
E621365
|
entity |
| Predicate | traditionalTerritoryUse |
P116633
|
FINISHED |
| Object | hunting grounds |
—
|
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: hunting grounds | Statement: [Waiwai, traditionalTerritoryUse, hunting grounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalTerritoryUse Context triple: [Waiwai, traditionalTerritoryUse, hunting grounds]
-
A.
territorialUse
Indicates the use, control, or occupation of a geographic area or territory by an entity.
-
B.
traditionalUseRegion
chosen
Indicates the geographic region where something has been traditionally used or practiced.
-
C.
traditionalTerritorialDesignation
Indicates a historically or culturally recognized claim or assignment of a geographic area to a particular group, authority, or identity.
-
D.
traditionalUse
Indicates that something is used or practiced according to long-established customs, habits, or cultural traditions.
-
E.
traditionalUseDomain
Indicates that something is traditionally used or applied within a particular domain, field, or area of practice.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 5:16 a.m.