Triple
T5556813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lipotes |
E145663
|
entity |
| Predicate | hasLocomotionType |
P23273
|
FINISHED |
| Object | aquatic swimming |
—
|
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: aquatic swimming | Statement: [Lipotes, hasLocomotionType, aquatic swimming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocomotionType Context triple: [Lipotes, hasLocomotionType, aquatic swimming]
-
A.
hasMovementType
chosen
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
-
B.
hasLocomotive
Indicates that one entity possesses or is equipped with a locomotive as part of its composition or operation.
-
C.
locomotion
Indicates movement or the ability to move from one place to another.
-
D.
hasMotivePowerType
Indicates that an entity (such as a vehicle or machine) operates using a specified type of motive power (e.g., electric, diesel, steam).
-
E.
supportsMobilityType
Indicates that one entity provides compatibility with, or can function using, a specified type of mobility or movement mode.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01ffe12cc81908186f28ace0f4d82 |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.