Triple
T34804611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daddy Johnson |
E1003318
|
entity |
| Predicate | familyEconomicStatus |
P2987
|
FINISHED |
| Object | poor |
—
|
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: poor | Statement: [Daddy Johnson, familyEconomicStatus, poor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyEconomicStatus Context triple: [Daddy Johnson, familyEconomicStatus, poor]
-
A.
economicStatus
chosen
Indicates the financial or socioeconomic condition or standing of an entity relative to others or to defined economic criteria.
-
B.
householdIncome
Indicates the monetary income received by a household, typically over a specified period such as a year.
-
C.
hasEconomicLevel
Indicates that one entity possesses, is classified by, or is associated with a particular economic status or level.
-
D.
householdStatus
Indicates the type or condition of a person’s living arrangement within a household, such as their role, membership, or current residency status.
-
E.
socioEconomicBase
Indicates a foundational socio-economic relationship where one entity serves as the economic or social basis, support, or underlying structure for another.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 3:59 p.m.