Triple
T1998021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tylopoda |
E43400
|
entity |
| Predicate | locomotionType |
P6160
|
FINISHED |
| Object | unguligrade with pad support |
—
|
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: unguligrade with pad support | Statement: [Tylopoda, locomotionType, unguligrade with pad support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locomotionType Context triple: [Tylopoda, locomotionType, unguligrade with pad support]
-
A.
locomotion
Indicates movement or the ability to move from one place to another.
-
B.
movementType
chosen
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
C.
mobilityCharacteristic
Indicates a relationship where an entity is described or classified in terms of its movement or transportation-related properties, such as how, how well, or under what conditions it can move or be moved.
-
D.
hasLocomotive
Indicates that one entity possesses or is equipped with a locomotive as part of its composition or operation.
-
E.
hasLegType
Indicates that an entity possesses a specific type or category of legs.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb91055d88190a980e7b42e5895d4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb79c97d48190b3147430ed39faa9 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.