Triple
T31249943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hypotaenidia |
E796787
|
entity |
| Predicate | typicalFlightAbility |
P3594
|
FINISHED |
| Object | flightless or weak-flying |
—
|
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: flightless or weak-flying | Statement: [Hypotaenidia, typicalFlightAbility, flightless or weak-flying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFlightAbility Context triple: [Hypotaenidia, typicalFlightAbility, flightless or weak-flying]
-
A.
flightAbility
chosen
Indicates the capability or potential of an entity to fly or engage in powered or unpowered aerial movement.
-
B.
natureOfFlight
Indicates the general type or characteristics of a flight, such as its purpose, category, or operational nature.
-
C.
aircraftCapability
Indicates that an aircraft possesses a particular capability, function, or operational feature.
-
D.
airCapability
Indicates that an entity possesses the ability or resources to operate or project power in the air (e.g., through aircraft, air defenses, or related systems).
-
E.
typicalAircraftStrength
Indicates the usual or characteristic level of military strength or capability associated with an aircraft.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:11 p.m.