Triple
T2092471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polynesian outliers |
E32700
|
entity |
| Predicate | hasNavigationTechnology |
P35891
|
FINISHED |
| Object | outrigger canoes |
—
|
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: outrigger canoes | Statement: [Polynesian outliers, hasNavigationTechnology, outrigger canoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationTechnology Context triple: [Polynesian outliers, hasNavigationTechnology, outrigger canoes]
-
A.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
B.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
C.
hasNave
Indicates that one entity (typically a building or structure) possesses or includes a nave as a distinct architectural part.
-
D.
hasNavigationClearance
Indicates that an entity has been granted authorization to navigate through a specified area or along a particular route.
-
E.
hasNavigationHazard
Indicates that something presents or contains a condition, object, or feature that poses a risk or obstacle to safe navigation.
- F. None of above. chosen
Provenance (4 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba774ca881909f83cf65ffeb24bb |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abba2e65b48190bb19cfc4b0f8c462 |
completed | March 7, 2026, 5:39 a.m. |
Created at: March 4, 2026, 7:43 p.m.