Triple
T30864427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Shield Stamps showrooms |
E786156
|
entity |
| Predicate | customerActivity |
P148841
|
FINISHED |
| Object | browsing catalogues in-store |
—
|
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: browsing catalogues in-store | Statement: [Green Shield Stamps showrooms, customerActivity, browsing catalogues in-store]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customerActivity Context triple: [Green Shield Stamps showrooms, customerActivity, browsing catalogues in-store]
-
A.
playerActivities
Indicates the various actions, events, or engagements that a player participates in within a given context or system.
-
B.
targetUserActivity
Indicates that a specific user is the intended recipient or focus of a particular activity or action.
-
C.
usedActivity
chosen
Indicates that an entity performed or engaged in a particular activity.
-
D.
hasRecentActivity
Indicates that the subject has performed an action or been involved in an event within a defined recent time period.
-
E.
evidenceOfActivity
Indicates that there is information or data supporting the occurrence or performance of a particular activity or action.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691ab31288190afe04c1a55477a9f |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:47 p.m.