Triple
T9621752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Plateau |
E232357
|
entity |
| Predicate | hasSocioeconomicStatus |
P2987
|
FINISHED |
| Object | low income |
—
|
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: low income | Statement: [Central Plateau, hasSocioeconomicStatus, low income]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocioeconomicStatus Context triple: [Central Plateau, hasSocioeconomicStatus, low income]
-
A.
hasSocioeconomicIssue
Indicates that an entity is affected by, associated with, or involved in a socioeconomic problem or challenge.
-
B.
hasSocioEconomicContext
Indicates the broader social and economic conditions or circumstances within which an entity, event, or relationship occurs or is interpreted.
-
C.
economicStatus
chosen
Indicates the financial or socioeconomic condition or standing of an entity relative to others or to defined economic criteria.
-
D.
subjectSocialStatus
Indicates the social standing or rank that the subject holds within a society or group.
-
E.
socialClassAtBirth
Indicates the social class or socioeconomic status into which an individual was born.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9ad505588190b8c81ce09f1904ec |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.