Triple
T19052141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black eagle |
E466286
|
entity |
| Predicate | hasFlightCharacteristic |
P134910
|
FINISHED |
| Object | powerful flight |
—
|
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: powerful flight | Statement: [Black eagle, hasFlightCharacteristic, powerful flight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlightCharacteristic Context triple: [Black eagle, hasFlightCharacteristic, powerful flight]
-
A.
takeoffCharacteristic
Indicates the specific properties or conditions associated with how an entity takes off, such as its manner, performance, or requirements during takeoff.
-
B.
hasLandingCharacteristics
Indicates that an entity possesses specific attributes or features related to how it lands or is capable of landing.
-
C.
aircraftCapability
Indicates that an aircraft possesses a particular capability, function, or operational feature.
-
D.
hasTypeOfFlights
Indicates that an entity offers, includes, or is associated with specific categories or kinds of flights.
-
E.
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).
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc031ff881908e8c68c7aaff3733 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4c0fc3c4c8190abbfe06e1bd3325c |
completed | April 19, 2026, 11:48 a.m. |
Created at: April 10, 2026, 12:03 p.m.