Triple
T34239700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAe ATP |
E878427
|
entity |
| Predicate | serviceCeiling_m_approx |
P193147
|
FINISHED |
| Object | 7600 |
—
|
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: 7600 | Statement: [BAe ATP, serviceCeiling_m_approx, 7600]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceCeiling_m_approx Context triple: [BAe ATP, serviceCeiling_m_approx, 7600]
-
A.
serviceCeilingFeet
Indicates the maximum altitude, measured in feet, at which an aircraft or vehicle can effectively operate or provide service.
-
B.
serviceCeilingContribution
Indicates the maximum level or limit of service that an entity is allowed or expected to provide as its contribution.
-
C.
maximumCeiling
Indicates the highest allowable or achievable limit or value that something cannot exceed.
-
D.
operationalCeiling
Indicates the maximum altitude at which an entity (such as an aircraft or system) is designed or permitted to operate effectively and safely.
-
E.
ceilingBasedOn
Indicates that one entity’s maximum limit or upper bound is determined or constrained by another entity.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: May 1, 2026, 1:56 a.m.