Triple
T3918283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Admirals Club |
E88896
|
entity |
| Predicate | primaryUserBase |
P7221
|
FINISHED |
| Object | American Airlines passengers |
—
|
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: American Airlines passengers | Statement: [Admirals Club, primaryUserBase, American Airlines passengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUserBase Context triple: [Admirals Club, primaryUserBase, American Airlines passengers]
-
A.
primaryUser
Indicates that the referenced user is the main or principal user associated with a given account, resource, or context.
-
B.
primaryUserGroup
Indicates the main or default user group to which a user is primarily assigned or associated.
-
C.
userBase
chosen
Indicates that one entity serves as the primary or foundational group of users associated with another entity.
-
D.
primaryClient
Indicates that one entity serves as the main or most important client associated with another entity.
-
E.
primaryService
Indicates that one entity serves as the main or principal service provided or used in relation to 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.