Triple
T27079384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo naledi |
E685550
|
entity |
| Predicate | climbingAdaptations |
P123709
|
FINISHED |
| Object | present in upper limbs |
—
|
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: present in upper limbs | Statement: [Homo naledi, climbingAdaptations, present in upper limbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingAdaptations Context triple: [Homo naledi, climbingAdaptations, present in upper limbs]
-
A.
climbingMechanism
Indicates a mechanism or method by which an entity ascends or climbs another surface or structure.
-
B.
climbPerformance
Indicates how effectively or rapidly an entity ascends or gains altitude relative to conditions or expectations.
-
C.
climbCharacteristic
chosen
Indicates a characteristic or property related to how an entity climbs or performs climbing actions.
-
D.
climbingUse
Indicates that an entity uses or employs another entity as equipment, support, or aid specifically for climbing activities.
-
E.
climbingHabit
Indicates a relationship where an entity has a tendency or behavior of climbing, such as regularly ascending surfaces, structures, or other objects.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 8:33 a.m.