Triple
T31563866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Bullock |
E805347
|
entity |
| Predicate | economicConcern |
P2313
|
FINISHED |
| Object | family overspending |
—
|
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: family overspending | Statement: [Alexander Bullock, economicConcern, family overspending]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicConcern Context triple: [Alexander Bullock, economicConcern, family overspending]
-
A.
economicView
Indicates a relationship where one entity holds or expresses a particular economic belief, stance, or perspective regarding economic systems, policies, or issues.
-
B.
economicAspect
chosen
Indicates that something is related to, characterized by, or has implications for economic factors, conditions, or outcomes.
-
C.
economicFunction
Indicates the role or purpose an entity serves within an economic system, such as how it contributes to production, distribution, or consumption of goods and services.
-
D.
economicGoal
Indicates that an entity has a targeted economic outcome or objective it aims to achieve.
-
E.
economicTrend
Indicates the general direction or pattern of economic activity or conditions over a period of time.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 30, 2026, 10:16 p.m.