Triple
T24830211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 11/29 |
E621315
|
entity |
| Predicate | servesAircraftType |
P70100
|
FINISHED |
| Object | small business jets |
—
|
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: small business jets | Statement: [Runway 11/29, servesAircraftType, small business jets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAircraftType Context triple: [Runway 11/29, servesAircraftType, small business jets]
-
A.
servesAviationType
Indicates that one entity provides services or functions specifically for a particular type or category of aviation.
-
B.
supportsAircraft
chosen
Indicates that one entity is capable of accommodating, carrying, or enabling the operation of an aircraft.
-
C.
usedByAircraftType
Indicates that something (such as equipment, infrastructure, or a procedure) is employed or operated by a specific type or category of aircraft.
-
D.
aircraftRoleSupported
Indicates that a given role or function is supported or enabled for a particular aircraft.
-
E.
appliesToAircraftFamily
Indicates that a rule, condition, or characteristic is relevant to, or valid for, an entire family or series of related aircraft models.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 18, 2026, 5:14 a.m.