Triple
T10957164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippopotamoidea |
E258875
|
entity |
| Predicate | limbPosture |
P26649
|
FINISHED |
| Object | tetrapod with pillar-like limbs in many members |
—
|
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: tetrapod with pillar-like limbs in many members | Statement: [Hippopotamoidea, limbPosture, tetrapod with pillar-like limbs in many members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limbPosture Context triple: [Hippopotamoidea, limbPosture, tetrapod with pillar-like limbs in many members]
-
A.
limbType
Indicates the specific kind or category of limb associated with an entity (e.g., arm, leg, wing, fin).
-
B.
limbMorphology
chosen
Indicates the structural form, shape, and configuration of an organism’s limbs in relation to its body.
-
C.
hasLimb
Indicates that an entity possesses a specific limb as part of its body.
-
D.
proceduralPosture
Indicates the current stage or status of a legal case within the judicial or administrative process at the time it is being considered or described.
-
E.
hasLimbs
Indicates that an entity possesses one or more limbs as physical appendages.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771260e9881909401a7a7466e1b8a |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.