Triple
T37606023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jabirr Jabirr people |
E935652
|
entity |
| Predicate | traditionalKnowledgeIncludes |
P178758
|
FINISHED |
| Object | navigation of coastal waters |
—
|
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: navigation of coastal waters | Statement: [Jabirr Jabirr people, traditionalKnowledgeIncludes, navigation of coastal waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalKnowledgeIncludes Context triple: [Jabirr Jabirr people, traditionalKnowledgeIncludes, navigation of coastal waters]
-
A.
traditionalKnowledgeArea
chosen
Indicates that something pertains to, or falls within, a specific domain or field of traditional knowledge.
-
B.
traditionalUse
Indicates that something is used or practiced according to long-established customs, habits, or cultural traditions.
-
C.
traditionalUseDomain
Indicates that something is traditionally used or applied within a particular domain, field, or area of practice.
-
D.
traditionalUseSince
Indicates that something has been used in a traditional way starting from a specified point in time.
-
E.
traditionalUseRegion
Indicates the geographic region where something has been traditionally used or practiced.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc89596d08190b97bd60b45c7f9c0 |
completed | May 9, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69ffc81ba5dc8190ae94d44e2284948f |
completed | May 9, 2026, 11:49 p.m. |
Created at: May 3, 2026, 4:18 p.m.