Triple
T18106504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hikianalia |
E433357
|
entity |
| Predicate | usesNavigationMethod |
P8588
|
FINISHED |
| Object | traditional Polynesian wayfinding |
—
|
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: traditional Polynesian wayfinding | Statement: [Hikianalia, usesNavigationMethod, traditional Polynesian wayfinding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesNavigationMethod Context triple: [Hikianalia, usesNavigationMethod, traditional Polynesian wayfinding]
-
A.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
B.
navigatesUsing
chosen
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
-
C.
usedToNavigate
Indicates that one entity served as a means or tool for another entity to find or follow a route or direction.
-
D.
hasNavigationPurpose
Indicates that something exists or is designed specifically to serve a navigational function or goal.
-
E.
hasNavigationRegime
Indicates that an entity is subject to or governed by a particular navigation regime or set of navigational rules.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddba6b288190af9a5d9c32d16e98 |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.