Triple
T16627710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peoria County, Illinois |
E403991
|
entity |
| Predicate | hasMajorIndustryPresence |
P53279
|
FINISHED |
| Object | healthcare |
—
|
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: healthcare | Statement: [Peoria County, Illinois, hasMajorIndustryPresence, healthcare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorIndustryPresence Context triple: [Peoria County, Illinois, hasMajorIndustryPresence, healthcare]
-
A.
hasMajorEmployer
Indicates that an entity has a primary or most significant employer with which it is chiefly affiliated for work or occupation.
-
B.
containsIndustry
chosen
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
C.
hasNoMajorIndustry
Indicates that the referenced place or entity does not possess any dominant or significant industrial sector.
-
D.
hasIndustrialSector
Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
-
E.
hasPrincipalIndustry
Indicates that an entity’s main or primary industry of operation is the specified industry.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e378e2683481908c9a5ed895a09a6e |
completed | April 18, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.