Triple
T7153158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Executive Club |
E166741
|
entity |
| Predicate | hasHouseholdFeature |
P75164
|
FINISHED |
| Object | allows household accounts to pool Avios |
—
|
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: allows household accounts to pool Avios | Statement: [Executive Club, hasHouseholdFeature, allows household accounts to pool Avios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHouseholdFeature Context triple: [Executive Club, hasHouseholdFeature, allows household accounts to pool Avios]
-
A.
hasHouseholdType
Indicates the type or category of household associated with an entity (e.g., family, single-person, shared, etc.).
-
B.
hasResidenceFeature
Indicates that a residence possesses or is characterized by a specific feature or attribute.
-
C.
hasInteriorFeature
Indicates that an entity contains or includes a specific feature within its interior space.
-
D.
hasHouse
Indicates that one entity possesses, owns, or is provided with a house in relation to another entity.
-
E.
hasTopFloorFeature
Indicates that a building’s top floor possesses a specific feature, attribute, or amenity.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f52c1081908c4fa424d5e965bc |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:46 p.m.