Triple
T217798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryanair |
E4144
|
entity |
| Predicate | baggagePolicy |
P1051
|
FINISHED |
| Object | fees for checked baggage |
—
|
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: fees for checked baggage | Statement: [Ryanair, baggagePolicy, fees for checked baggage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baggagePolicy Context triple: [Ryanair, baggagePolicy, fees for checked baggage]
-
A.
hasBaggageSystem
Indicates that an entity is equipped with or utilizes a baggage handling system.
-
B.
airSupport
Indicates that one entity provides aerial assistance or backing to another, typically through aircraft-based protection, transport, or attack.
-
C.
hasCustomsAndImmigration
Indicates that customs and immigration control services are present or provided at a given location or facility.
-
D.
governingPolicy
chosen
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
E.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c5062e48190833be10e4770e1e9 |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5357bc8190b29a48e3053fb76d |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.