Triple
T19578043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avro Canada CF-105 Arrow |
E489911
|
entity |
| Predicate | designedServiceCeiling |
P75760
|
FINISHED |
| Object | over 50,000 ft |
—
|
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: over 50,000 ft | Statement: [Avro Canada CF-105 Arrow, designedServiceCeiling, over 50,000 ft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedServiceCeiling Context triple: [Avro Canada CF-105 Arrow, designedServiceCeiling, over 50,000 ft]
-
A.
ceilingBasedOn
Indicates that one entity’s maximum limit or upper bound is determined or constrained by another entity.
-
B.
serviceCeilingContribution
Indicates the maximum level or limit of service that an entity is allowed or expected to provide as its contribution.
-
C.
operationalCeiling
Indicates the maximum altitude at which an entity (such as an aircraft or system) is designed or permitted to operate effectively and safely.
-
D.
serviceCeilingFeet
chosen
Indicates the maximum altitude, measured in feet, at which an aircraft or vehicle can effectively operate or provide service.
-
E.
maximumCeiling
Indicates the highest allowable or achievable limit or value that something cannot exceed.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e64025d5d081909dbb0c079d366006 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.