Triple
T35820640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 24R at LAX |
E1035488
|
entity |
| Predicate | supportsWidebodyAircraft |
P5536
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Runway 24R at LAX, supportsWidebodyAircraft, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsWidebodyAircraft Context triple: [Runway 24R at LAX, supportsWidebodyAircraft, true]
-
A.
supportsWideBodyAircraft
chosen
Indicates that an entity (such as an airport, runway, or gate) is capable of accommodating and handling wide-body aircraft operations.
-
B.
supportsNarrowBodyAircraft
Indicates that one entity is capable of accommodating, servicing, or being compatible with narrow-body aircraft.
-
C.
supportsAircraft
Indicates that one entity is capable of accommodating, carrying, or enabling the operation of an aircraft.
-
D.
hasWideBodyVariant
Indicates that an entity has a corresponding wide-body version or variant of itself.
-
E.
supportsSingleEngineAircraft
Indicates that the subject is designed, equipped, or authorized to accommodate or be compatible with single-engine aircraft.
- 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.