Triple
T3291567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawthorne Works |
E69112
|
entity |
| Predicate | socioEconomicRole |
P2223
|
FINISHED |
| Object | major employer in Cicero, Illinois |
—
|
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: major employer in Cicero, Illinois | Statement: [Hawthorne Works, socioEconomicRole, major employer in Cicero, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socioEconomicRole Context triple: [Hawthorne Works, socioEconomicRole, major employer in Cicero, Illinois]
-
A.
hasEconomicRole
chosen
Indicates that an entity participates in or fulfills a specific function, position, or responsibility within an economic system or activity.
-
B.
urbanRole
Indicates the function, status, or role that an entity holds within an urban or city context.
-
C.
ethnicRole
Indicates a role, function, or social position that is specifically associated with or defined by an entity’s ethnicity.
-
D.
employedRole
Indicates that an entity holds or performs a specific role or position within an employment or work context.
-
E.
economicStatus
Indicates the financial or socioeconomic condition or standing of an entity relative to others or to defined economic criteria.
- 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_69ad859d45748190b0742408c954b39f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb05d0c908190a927d1af78e27de0 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.