Triple
T6011865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunchback |
E133852
|
entity |
| Predicate | aircraftRange |
P57459
|
FINISHED |
| Object | approximately 2,000 km |
—
|
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: approximately 2,000 km | Statement: [Hunchback, aircraftRange, approximately 2,000 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftRange Context triple: [Hunchback, aircraftRange, approximately 2,000 km]
-
A.
aircraftLength
Indicates the physical longitudinal measurement of an aircraft from its nose to its tail.
-
B.
flightRangeFocus
chosen
Indicates that the relationship centers on the range or distance a flight can cover, emphasizing limitations or focus on how far the flight can travel.
-
C.
aircraftCapability
Indicates that an aircraft possesses a particular capability, function, or operational feature.
-
D.
aircraftCapacity
Indicates the maximum number of passengers or amount of load that an aircraft is designed or allowed to carry.
-
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.
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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f5159bc8190a988293bbbb99d24 |
completed | March 22, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.