Triple
T6694989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macropodiformes |
E152725
|
entity |
| Predicate | hindlimbFunction |
P3596
|
FINISHED |
| Object | locomotion by hopping |
—
|
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: locomotion by hopping | Statement: [Macropodiformes, hindlimbFunction, locomotion by hopping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hindlimbFunction Context triple: [Macropodiformes, hindlimbFunction, locomotion by hopping]
-
A.
limbMorphology
Indicates the structural form, shape, and configuration of an organism’s limbs in relation to its body.
-
B.
limbType
Indicates the specific kind or category of limb associated with an entity (e.g., arm, leg, wing, fin).
-
C.
lostLimb
Indicates that an entity has had one or more of its limbs removed or rendered permanently absent, typically as a result of injury, surgery, or trauma.
-
D.
locomotion
chosen
Indicates movement or the ability to move from one place to another.
-
E.
legs
Indicates that an entity possesses legs, specifying the presence or number of leg-like appendages associated with it.
- 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_69c6880687b08190805278b504d1c92c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6b5ed99e48190970805225458ce82 |
completed | March 27, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0e1d348190af1762ea1951038e |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:05 p.m.