Triple
T2229924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lufthansa |
E48740
|
entity |
| Predicate | isFlagCarrier |
P3074
|
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: [Lufthansa, isFlagCarrier, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFlagCarrier Context triple: [Lufthansa, isFlagCarrier, true]
-
A.
servesAsHubForFlagCarrierOf
Indicates that a location or facility functions as a primary hub for the national flag carrier airline of a given country or region.
-
B.
carrierOf
Indicates that one entity serves as the medium, vehicle, or host that contains, transports, or conveys another entity.
-
C.
flagshipFor
Indicates that one entity serves as the primary or leading representative example for another entity, often embodying its most important qualities or status.
-
D.
nationalAirline
chosen
Indicates that an airline serves as the official or primary flag carrier of a particular country.
-
E.
flagshipCarrierOf
Indicates that one entity serves as the primary or most prominent carrier (such as an airline or telecommunications provider) representing or associated with another entity, typically a country, brand, or organization.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc069e0ac8190bcda8cba9f5c7a5d |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.