Triple
T248181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | harpy eagle |
E5082
|
entity |
| Predicate | flightStyle |
P8770
|
FINISHED |
| Object | soaring and short powerful flights |
—
|
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: soaring and short powerful flights | Statement: [harpy eagle, flightStyle, soaring and short powerful flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightStyle Context triple: [harpy eagle, flightStyle, soaring and short powerful flights]
-
A.
flightAbility
Indicates the capability or potential of an entity to fly or engage in powered or unpowered aerial movement.
-
B.
wingConfiguration
Indicates how the wings of an aircraft or creature are arranged or structured relative to its body and to each other.
-
C.
flightRegime
Indicates the operational conditions or phase of flight under which an aircraft or aerospace vehicle is functioning (e.g., speed, altitude, and atmospheric regime).
-
D.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
E.
styleOfPlay
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d154ebc819087a5c9dc4f62ff44 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b64ea3081908de626a0e1445bdb |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c2ca46c81908c61696f31e59a98 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.