Triple
T35676625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Alliance partner flights (with varying benefits) |
E1030876
|
entity |
| Predicate | ticketMayBeIssuedBy |
P139894
|
FINISHED |
| Object | marketing carrier |
—
|
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: marketing carrier | Statement: [Star Alliance partner flights (with varying benefits), ticketMayBeIssuedBy, marketing carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketMayBeIssuedBy Context triple: [Star Alliance partner flights (with varying benefits), ticketMayBeIssuedBy, marketing carrier]
-
A.
ticketedBy
chosen
Indicates that an entity has been issued or assigned a ticket by another entity (such as an authority, system, or agent).
-
B.
ticket
Indicates that an entity serves as or is associated with a ticket, typically representing authorization, access, or a record for an event, service, or transaction.
-
C.
isIssued
Indicates that an authoritative source formally provides, distributes, or makes something (such as a document, order, or item) officially available to a recipient.
-
D.
ticketOfTarget
Indicates that one entity is a ticket associated with, or issued for, a specific target entity.
-
E.
isIssuedFor
Indicates that something (such as a document, order, or item) has been formally created, authorized, or provided for a specific purpose, recipient, or use.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:05 p.m.