Triple
T10102662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shopping Leblon |
E216239
|
entity |
| Predicate | servesClientele |
P9906
|
FINISHED |
| Object | upper-middle-class customers |
—
|
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: upper-middle-class customers | Statement: [Shopping Leblon, servesClientele, upper-middle-class customers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesClientele Context triple: [Shopping Leblon, servesClientele, upper-middle-class customers]
-
A.
servesCustomer
chosen
Indicates that one entity provides service, assistance, or products to another entity in the role of a customer.
-
B.
servesUsers
Indicates that an entity provides services, functionality, or benefits to one or more users.
-
C.
professionServed
Indicates that an entity has performed work or provided services in a particular profession or occupational role.
-
D.
intendedToServe
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
-
E.
servesAtThePleasureOf
Indicates that one entity holds a position or role that can be terminated at any time by another entity, typically at the discretion or will of that other entity.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd09af07c819099774af46ebf62d7 |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:02 p.m.