Triple
T11457925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carib |
E271578
|
entity |
| Predicate | navigationalSkill |
P35892
|
FINISHED |
| Object | open-sea voyaging |
—
|
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: open-sea voyaging | Statement: [Carib, navigationalSkill, open-sea voyaging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationalSkill Context triple: [Carib, navigationalSkill, open-sea voyaging]
-
A.
navigationalAchievement
Indicates the successful completion of a significant navigation-related task or milestone, such as accurately traversing a route or reaching a designated destination.
-
B.
navigability
Indicates how easily and effectively something (such as a space, interface, or route) can be traversed or moved through.
-
C.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
D.
usedToNavigate
Indicates that one entity served as a means or tool for another entity to find or follow a route or direction.
-
E.
hasNavigationKnowledge
chosen
Indicates that an entity possesses information or expertise related to navigating or determining routes within an environment or system.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f2138081909408c7916cef99c9 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.