Triple
T31489688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portrait of Madame M. |
E803372
|
entity |
| Predicate | subjectHasSocialClass |
P27958
|
FINISHED |
| Object | upper class |
—
|
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 class | Statement: [Portrait of Madame M., subjectHasSocialClass, upper class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectHasSocialClass Context triple: [Portrait of Madame M., subjectHasSocialClass, upper class]
-
A.
associatedWithSocialClass
chosen
Indicates a relationship in which an entity is linked or connected to a particular social class or socioeconomic stratum.
-
B.
socialClassSystem
Indicates a hierarchical organization of people into social classes based on status, power, or economic position.
-
C.
socialClassPosition
Indicates the relative social status or rank an entity holds within a social hierarchy or class structure.
-
D.
socialClassContext
Indicates the social class or socioeconomic background within which an action, relationship, or situation occurs or is interpreted.
-
E.
socialClassAfterWealth
Indicates that an entity’s social class or status is determined or updated based on its level of wealth.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 30, 2026, 9:37 p.m.