Triple
T18400381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Dehesa area |
E449976
|
entity |
| Predicate | socioeconomicStratum |
P119493
|
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: [La Dehesa area, socioeconomicStratum, upper class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socioeconomicStratum Context triple: [La Dehesa area, socioeconomicStratum, upper class]
-
A.
socioEconomicBase
Indicates a foundational socio-economic relationship where one entity serves as the economic or social basis, support, or underlying structure for another.
-
B.
socialClassPosition
chosen
Indicates the relative social status or rank an entity holds within a social hierarchy or class structure.
-
C.
socialClassSystem
Indicates a hierarchical organization of people into social classes based on status, power, or economic position.
-
D.
socioeconomicRole
Indicates the social and economic position, function, or status an entity holds within a society or system.
-
E.
economicStatus
Indicates the financial or socioeconomic condition or standing of an entity relative to others or to defined economic criteria.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e5194f2a8c8190afcd7db23e3795fb |
completed | April 19, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.