Triple
T3975897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiribati people |
E85640
|
entity |
| Predicate | navigationSkill |
P12979
|
FINISHED |
| Object | traditional 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 wayfinding | Statement: [Kiribati people, navigationSkill, traditional wayfinding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationSkill Context triple: [Kiribati people, navigationSkill, traditional wayfinding]
-
A.
navigation
chosen
Indicates the act or process of determining and following a path or route from one location or state to another.
-
B.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
C.
mapLocation
Indicates a relationship where an entity is associated with a specific position or area on a map.
-
D.
navigationRegulation
Indicates rules or constraints that govern how navigation or movement is allowed, restricted, or managed within a particular space or system.
-
E.
navigationSystemComponent
Indicates that one entity functions as a component or subpart of a navigation system associated with another entity.
- 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.