Triple
T28026930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moti Bazaar, Rawalpindi |
E708148
|
entity |
| Predicate | shoppingTheme |
P90808
|
FINISHED |
| Object | festive clothing |
—
|
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: festive clothing | Statement: [Moti Bazaar, Rawalpindi, shoppingTheme, festive clothing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shoppingTheme Context triple: [Moti Bazaar, Rawalpindi, shoppingTheme, festive clothing]
-
A.
shoppingStyle
Indicates the manner or approach an entity typically uses when shopping, such as their preferred methods, habits, or decision-making style.
-
B.
shopSection
Indicates the specific section or area within a shop where an item, activity, or service is located or takes place.
-
C.
purchaseContext
Indicates the circumstances, conditions, or situational details under which a purchase occurs or is made.
-
D.
shopSpecialty
chosen
Indicates that a shop primarily focuses on or is specially known for offering a particular type of product or service.
-
E.
buyIn
Indicates that one party purchases or acquires an ownership stake, participation, or commitment in something initiated or owned by another party.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:13 p.m.