Triple
T14029814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heideveld |
E337556
|
entity |
| Predicate | socialClassProfile |
P87215
|
FINISHED |
| Object | working-class community |
—
|
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: working-class community | Statement: [Heideveld, socialClassProfile, working-class community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialClassProfile Context triple: [Heideveld, socialClassProfile, working-class community]
-
A.
socialClassContext
chosen
Indicates the social class or socioeconomic background within which an action, relationship, or situation occurs or is interpreted.
-
B.
socialClassSystem
Indicates a hierarchical organization of people into social classes based on status, power, or economic position.
-
C.
socialClassAspiration
Indicates a desire or intention by one entity to attain a higher or different social class or status than its current one.
-
D.
socialClassAtBirth
Indicates the social class or socioeconomic status into which an individual was born.
-
E.
socialClassAtStart
Indicates the social class or socioeconomic status an entity belongs to at the beginning of a specified period, event, or process.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fa9f8248190930954d609dee5f1 |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.