Triple
T29977049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galela people |
E761476
|
entity |
| Predicate | traditionalNavigationSkills |
P194944
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Galela people, traditionalNavigationSkills, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalNavigationSkills Context triple: [Galela people, traditionalNavigationSkills, yes]
-
A.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
B.
trailUses
Indicates that a trail supports or is designated for specific types of use or activities (such as hiking, biking, or horseback riding).
-
C.
trailAccess
Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific trail or pathway.
-
D.
helpsHimNavigate
Indicates that one entity assists another male entity in finding or moving along a path or route.
-
E.
navigationalAdaptation
Indicates how an entity adjusts its navigation or movement behavior in response to environmental conditions or contextual changes.
- 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
| PDg | Predicate description generation | batch_69fd91a44268819081b372296e3aa116 |
completed | May 8, 2026, 7:32 a.m. |
Created at: April 29, 2026, 6:33 p.m.