Triple
T17943213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SU95 |
E448635
|
entity |
| Predicate | aircraftAlternativeUse |
P9620
|
FINISHED |
| Object | charter passenger flights |
—
|
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: charter passenger flights | Statement: [SU95, aircraftAlternativeUse, charter passenger flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftAlternativeUse Context triple: [SU95, aircraftAlternativeUse, charter passenger flights]
-
A.
aviationUsage
Indicates that something is used for, involved in, or associated with aviation-related activities or purposes.
-
B.
aircraftAlternativeName
Indicates that an aircraft is known by an alternative or additional name, designation, or alias.
-
C.
aircraft
Indicates that an entity is an aircraft or functions in the role of an aircraft in the described context.
-
D.
usedInAviationAs
chosen
Indicates that something serves a particular role, function, or application within the field of aviation.
-
E.
additionalAircraft
Indicates that one aircraft is an extra or supplementary aircraft associated with another aircraft or flight operation.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad97611c8190a861467ae51f6c48 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.