Triple
T32926612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQQ |
E842289
|
entity |
| Predicate | runwaySuitableFor |
P46124
|
FINISHED |
| Object | large aircraft |
—
|
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: large aircraft | Statement: [SQQ, runwaySuitableFor, large aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwaySuitableFor Context triple: [SQQ, runwaySuitableFor, large aircraft]
-
A.
runwaySupportsAircraftType
chosen
Indicates that a particular runway is suitable and certified for use by a specified type of aircraft.
-
B.
runwayRequirement
Indicates the minimum runway characteristics (such as length or surface conditions) needed for an aircraft or operation to take off or land safely.
-
C.
runwayUsedAs
Indicates that a particular runway is being utilized for a specific purpose, role, or operational function.
-
D.
runwayInformationAvailableIn
Indicates that information about a runway is available within or through a specified medium, source, or context.
-
E.
runwaysUsableAt
Indicates that certain runways at a location are available and suitable for use (e.g., for takeoff or landing) at a given time or under specified conditions.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 1:20 a.m.