Triple
T4421691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TVF |
E95111
|
entity |
| Predicate | airlineWebsite |
P55883
|
FINISHED |
| Object | https://www.transavia.com |
—
|
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: https://www.transavia.com | Statement: [TVF, airlineWebsite, https://www.transavia.com]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineWebsite Context triple: [TVF, airlineWebsite, https://www.transavia.com]
-
A.
airline
Indicates that an entity operates as a commercial air transport carrier providing flight services between locations.
-
B.
airlineHub
Indicates that a particular location (typically an airport or city) serves as a central hub or primary operational base for an airline.
-
C.
airlineType
Indicates the classification or category of an airline based on its operational or service characteristics.
-
D.
airlineBookingChannel
Indicates the method or platform through which an airline reservation is made or managed between a customer and the airline.
-
E.
hasAirlines
Indicates that one entity (such as an airport, city, or country) is served by or associated with one or more airline operators.
- F. None of above. chosen
Provenance (4 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554a0e7c8190b704d00d07b1857d |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:30 p.m.