Triple
T1549505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yucaipa, California |
E33054
|
entity |
| Predicate | medianHouseholdIncomeApproxUSD |
P23301
|
FINISHED |
| Object | 70000 |
—
|
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: 70000 | Statement: [Yucaipa, California, medianHouseholdIncomeApproxUSD, 70000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: medianHouseholdIncomeApproxUSD Context triple: [Yucaipa, California, medianHouseholdIncomeApproxUSD, 70000]
-
A.
medianHouseholdIncome
chosen
Indicates the typical (middle) value of income earned by households in a given area, such that half of households earn more and half earn less.
-
B.
medianHouseholdIncomeRank
Indicates the relative position of a household’s income compared to others, typically ordered from lowest to highest median income.
-
C.
incomeMeasure
Indicates a relationship where one entity serves as a measure or metric of another entity’s income.
-
D.
economicStatus
Indicates the financial or socioeconomic condition or standing of an entity relative to others or to defined economic criteria.
-
E.
numberOfHousingUnits
Indicates the total count of distinct housing units associated with an entity or within a specified area.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa574094048190a2d7fc3ac904d51e |
completed | March 6, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69a907b426dc8190975c024a50955368 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.