Triple
T20881398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commando |
E514158
|
entity |
| Predicate | hasServiceCeiling |
P75760
|
FINISHED |
| Object | approximately 24,500 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: approximately 24,500 ft | Statement: [Commando, hasServiceCeiling, approximately 24,500 ft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceCeiling Context triple: [Commando, hasServiceCeiling, approximately 24,500 ft]
-
A.
serviceCeilingFeet
chosen
Indicates the maximum altitude, measured in feet, at which an aircraft or vehicle can effectively operate or provide service.
-
B.
operationalCeiling
Indicates the maximum altitude at which an entity (such as an aircraft or system) is designed or permitted to operate effectively and safely.
-
C.
hasLimitedServiceType
Indicates that an entity is associated with a service that is restricted in scope, availability, or functionality compared to full or standard service types.
-
D.
hasCeilingType
Indicates that an entity is associated with or characterized by a specific type of ceiling.
-
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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c67a33548190b0f5ba58b001d387 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.