Triple
T30075743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAPI |
E764313
|
entity |
| Predicate | glidePathAngle |
P133654
|
FINISHED |
| Object | typically around 3 degrees |
—
|
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: typically around 3 degrees | Statement: [PAPI, glidePathAngle, typically around 3 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glidePathAngle Context triple: [PAPI, glidePathAngle, typically around 3 degrees]
-
A.
glideRatio
Indicates the ratio between horizontal distance traveled and vertical distance lost during a glide.
-
B.
inclinationAngle
chosen
Indicates the angle at which one object or reference frame is tilted or inclined relative to another specified baseline or plane.
-
C.
bendAngle
Indicates the degree to which one part is bent relative to another, typically measured as the angle formed at their joint or intersection.
-
D.
projectionAngle
Indicates the angle at which one entity is projected onto or relative to another reference (such as a line, plane, or direction).
-
E.
slopeAngleRange
Indicates the range of possible or allowed slope angles associated with a given entity or context.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d3da1608190aaf738cc69b73c26 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:01 p.m.