Triple
T26713258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oreopithecus |
E673478
|
entity |
| Predicate | skeletalAdaptation |
P161956
|
FINISHED |
| Object | mobile shoulder joint |
—
|
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: mobile shoulder joint | Statement: [Oreopithecus, skeletalAdaptation, mobile shoulder joint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skeletalAdaptation Context triple: [Oreopithecus, skeletalAdaptation, mobile shoulder joint]
-
A.
skeletalAdaptation
chosen
Indicates that an entity’s skeletal structure has changed or evolved in response to specific functional, environmental, or biomechanical demands.
-
B.
skeleton
Indicates that one entity serves as the basic structural framework or underlying support for another.
-
C.
limbMorphology
Indicates the structural form, shape, and configuration of an organism’s limbs in relation to its body.
-
D.
skeletonCoating
Indicates that one entity serves as a coating, covering, or outer layer on the skeleton of another entity.
-
E.
skeletonFeature
Indicates that one entity is a structural or anatomical skeletal feature or component of 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 3:36 a.m.