Triple
T33412243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uber Diamond |
E855617
|
entity |
| Predicate | userPerception |
P167371
|
FINISHED |
| Object | premium status |
—
|
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: premium status | Statement: [Uber Diamond, userPerception, premium status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userPerception Context triple: [Uber Diamond, userPerception, premium status]
-
A.
inUniversePerceptionByUsers
Indicates that the way something appears or is perceived is evaluated from the perspective of users within a specific fictional or defined universe.
-
B.
perceptionByHumans
chosen
Indicates that something is perceived, sensed, or experienced through human sensory or cognitive processes.
-
C.
typicalPerception
Indicates the usual or most common way an entity is perceived or experienced through the senses.
-
D.
influencedPerceptionOf
Indicates that one entity has affected, shaped, or altered how another entity is perceived or understood.
-
E.
publicPerception
Indicates how an individual, group, or entity is viewed, judged, or regarded by the general public or society at large.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e47f37848190aadb137c81760f1f |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.