Triple
T37601745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SM Hypermarket |
E935540
|
entity |
| Predicate | usesLoyaltyProgram |
P155797
|
FINISHED |
| Object | SM Advantage Card |
—
|
NE NERFINISHED |
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: SM Advantage Card | Statement: [SM Hypermarket, usesLoyaltyProgram, SM Advantage Card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLoyaltyProgram Context triple: [SM Hypermarket, usesLoyaltyProgram, SM Advantage Card]
-
A.
hasLoyalties
Indicates that an entity feels allegiance or commitment toward one or more other entities or causes.
-
B.
loyaltyProgramAccess
Indicates that an entity is granted rights or eligibility to participate in a specific loyalty or rewards program.
-
C.
supportsLoyaltyCards
Indicates that an entity provides functionality to accept, manage, or work with loyalty cards for rewards or benefits.
-
D.
loyaltyIncentive
Indicates a relationship where benefits or rewards are provided to encourage or recognize continued commitment or repeat engagement.
-
E.
loyaltyProgramLinkedTo
chosen
Indicates that a loyalty program is associated or connected to a particular entity, such that benefits, points, or rewards can be tracked or applied through that relationship.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.