Triple
T7944615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabre Corporation |
E184467
|
entity |
| Predicate | hasNotableClientType |
P79955
|
FINISHED |
| Object | network 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: network airlines | Statement: [Sabre Corporation, hasNotableClientType, network airlines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableClientType Context triple: [Sabre Corporation, hasNotableClientType, network airlines]
-
A.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
B.
hasClient
Indicates that an entity maintains a client relationship with another entity, typically as a provider of goods or services.
-
C.
hasNotableHost
Indicates that an entity is associated with a host who is particularly prominent, famous, or otherwise noteworthy.
-
D.
hasNotableNative
Indicates that an entity is known for having a notable person, species, or element that originates from or is native to it.
-
E.
hasNotableBearersType
Indicates that an entity has notable bearers belonging to a specified type or category.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b0e84448190a7e8e0749776a592 |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf788db1c8190839523e7777961d6 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:09 p.m.