Triple
T3105783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biedermeier |
E64825
|
entity |
| Predicate | hasSocialBase |
P6110
|
FINISHED |
| Object | urban middle 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: urban middle class | Statement: [Biedermeier, hasSocialBase, urban middle class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialBase Context triple: [Biedermeier, hasSocialBase, urban middle class]
-
A.
socialBase
chosen
Indicates a foundational social relationship or structure that underlies or supports interactions between entities.
-
B.
hasSocialIdentity
Indicates that an entity possesses or is associated with a particular social identity, such as a role, group membership, or socially recognized status.
-
C.
hasSocialGroup
Indicates that an entity belongs to, is associated with, or participates in a particular social group or community.
-
D.
hasVolunteerBase
Indicates that an entity maintains or relies on a group of volunteers as a foundational support resource.
-
E.
hasSocialDimension
Indicates that the relationship, attribute, or phenomenon involves social aspects, interactions, or implications among individuals or groups.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29beff08190b6e1eb6b0608d0eb |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:03 p.m.