Triple
T8861283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neornithes |
E210891
|
entity |
| Predicate | hasLocomotionMode |
P3596
|
FINISHED |
| Object | powered flight in most species |
—
|
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: powered flight in most species | Statement: [Neornithes, hasLocomotionMode, powered flight in most species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocomotionMode Context triple: [Neornithes, hasLocomotionMode, powered flight in most species]
-
A.
hasLocomotive
Indicates that one entity possesses or is equipped with a locomotive as part of its composition or operation.
-
B.
usesStructureForLocomotion
Indicates that an entity moves or travels by employing a particular physical structure or body part as its means of locomotion.
-
C.
supportsMobilityType
Indicates that one entity provides compatibility with, or can function using, a specified type of mobility or movement mode.
-
D.
hasPropulsionComponent
Indicates that an entity includes or is equipped with a component responsible for providing propulsion.
-
E.
locomotion
chosen
Indicates movement or the ability to move from one place to another.
- 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_69ca838bbddc8190ab546d737e5d350f |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e860888190a8a8702377db949e |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.