Triple
T14743750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar Airways Privilege Club |
E346413
|
entity |
| Predicate | familyPoolingName |
P115598
|
FINISHED |
| Object | Family Programme |
—
|
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: Family Programme | Statement: [Qatar Airways Privilege Club, familyPoolingName, Family Programme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyPoolingName Context triple: [Qatar Airways Privilege Club, familyPoolingName, Family Programme]
-
A.
allowsFamilyPooling
Indicates that one entity permits multiple related individuals to combine or share their resources, benefits, or access as a family unit.
-
B.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
-
C.
homePool
Indicates that an entity is associated with or belongs to a primary or default pool, typically used as its main or originating pool.
-
D.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
E.
familyAlliance
Indicates a cooperative or supportive relationship formed between families, often involving mutual obligations, shared interests, or joint actions.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7367a1c819081082cc355e385fa |
completed | April 14, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:30 a.m.