Triple
T25288682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaeropodidae |
E634017
|
entity |
| Predicate | forelimbMorphology |
P26649
|
FINISHED |
| Object | reduced number of functional toes |
—
|
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: reduced number of functional toes | Statement: [Chaeropodidae, forelimbMorphology, reduced number of functional toes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forelimbMorphology Context triple: [Chaeropodidae, forelimbMorphology, reduced number of functional toes]
-
A.
limbMorphology
chosen
Indicates the structural form, shape, and configuration of an organism’s limbs in relation to its body.
-
B.
forelimbFunction
Indicates the functional role or use of an entity’s forelimbs in performing actions or behaviors.
-
C.
limbType
Indicates the specific kind or category of limb associated with an entity (e.g., arm, leg, wing, fin).
-
D.
hasForelimbs
Indicates that an entity possesses front limbs or appendages used for movement, manipulation, or support.
-
E.
fossilMorphology
Indicates that one entity describes or characterizes the physical form and structural features of a fossil 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e0b00ec8190ae6c45f2ce24b727 |
completed | May 1, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:21 p.m.