Triple
T27004208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | whiptail wallaby |
E680194
|
entity |
| Predicate | locomotionAdaptation |
P84340
|
FINISHED |
| Object | elongated hind feet |
—
|
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: elongated hind feet | Statement: [whiptail wallaby, locomotionAdaptation, elongated hind feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locomotionAdaptation Context triple: [whiptail wallaby, locomotionAdaptation, elongated hind feet]
-
A.
locomotion
Indicates movement or the ability to move from one place to another.
-
B.
usesStructureForLocomotion
chosen
Indicates that an entity moves or travels by employing a particular physical structure or body part as its means of locomotion.
-
C.
hasHumanAdaptation
Indicates that something has been modified, designed, or adjusted specifically to suit human use, abilities, or needs.
-
D.
movementSubstrate
Indicates the medium or surface through which or on which an entity moves.
-
E.
hasAquaticAdaptationsIn
Indicates that an entity possesses physical or behavioral adaptations suited for living or functioning in a specified aquatic environment.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621d06a7c81908f80d005079262fd |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:59 a.m.