Triple
T2804385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aegean Airlines |
E54016
|
entity |
| Predicate | codeSharesWith |
P6096
|
FINISHED |
| Object | Star Alliance member airlines |
—
|
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: Star Alliance member airlines | Statement: [Aegean Airlines, codeSharesWith, Star Alliance member airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeSharesWith Context triple: [Aegean Airlines, codeSharesWith, Star Alliance member airlines]
-
A.
sharesCodebaseWith
Indicates that two software systems or components are built from, or depend on, substantially the same underlying source code.
-
B.
codeshareOperatesFor
chosen
Indicates that one airline operates a flight under a codeshare agreement on behalf of another airline, using the latter’s flight number or code.
-
C.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
D.
sharesModuleWith
Indicates that two entities are associated with or participate in at least one common module.
-
E.
sharesLibrariesWith
Indicates that two entities use or depend on at least one of the same libraries or library components.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde2ec2ac8190bd702ad3eafb6aed |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.