Triple
T14743659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Airways Executive Club |
E346411
|
entity |
| Predicate | supportsHouseholdAccount |
P5098
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [British Airways Executive Club, supportsHouseholdAccount, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHouseholdAccount Context triple: [British Airways Executive Club, supportsHouseholdAccount, true]
-
A.
supportsHouseholdLinking
Indicates that one entity enables or facilitates the creation or maintenance of an association between multiple household entities.
-
B.
supportsAccountType
chosen
Indicates that one entity is compatible with, or able to operate for, a specified type or category of account.
-
C.
holdsToAccount
Indicates that one entity is responsible for judging, challenging, or requiring justification from another entity for its actions or decisions.
-
D.
supportsSeparateAccounts
Indicates that one entity enables or allows the use or management of distinct, individually maintained accounts rather than a single shared account.
-
E.
hasHouseholdType
Indicates the type or category of household associated with an entity (e.g., family, single-person, shared, etc.).
- 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_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. |
Created at: April 10, 2026, 1:30 a.m.