Triple
T1493124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osphranter rufus |
E29625
|
entity |
| Predicate | hasTailFunction |
P28618
|
FINISHED |
| Object | balance during locomotion |
—
|
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: balance during locomotion | Statement: [Osphranter rufus, hasTailFunction, balance during locomotion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTailFunction Context triple: [Osphranter rufus, hasTailFunction, balance during locomotion]
-
A.
hasTail
Indicates that an entity possesses a tail as a physical attribute.
-
B.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
C.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
D.
hasTransportFunction
Indicates that an entity serves to move or carry something (such as people, goods, or signals) from one place or state to another.
-
E.
hasHook
Indicates that one entity possesses, is equipped with, or features a hook in relation to another entity or context.
- F. None of above. chosen
Provenance (4 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c665488190ae665f7a1b0563f5 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c52c703c8190a56389b09d97659f |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8:12 p.m.