Triple
T18700125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piaggio P.XI RC.40 |
E457224
|
entity |
| Predicate | designedForAltitudeRating |
P6750
|
FINISHED |
| Object | 4000 m |
—
|
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: 4000 m | Statement: [Piaggio P.XI RC.40, designedForAltitudeRating, 4000 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForAltitudeRating Context triple: [Piaggio P.XI RC.40, designedForAltitudeRating, 4000 m]
-
A.
operationalAltitude
Indicates the typical or designated altitude at which an entity is intended to operate.
-
B.
altitudeCapability
chosen
Indicates the maximum or typical altitude at which an entity can effectively operate or function.
-
C.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
D.
extendsToApproximateAltitude
Indicates that something reaches or stretches up to a specified altitude value, which is understood to be approximate rather than exact.
-
E.
cabinPressureAltitude
Indicates the altitude corresponding to the current cabin air pressure, as if that pressure were the standard atmospheric pressure at that height.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562eb06b481908ef9efdb976008f3 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.