Triple
T28126498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robinson, Illinois |
E710941
|
entity |
| Predicate | hasNotableIndustryType |
P13800
|
FINISHED |
| Object | food industry |
—
|
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: food industry | Statement: [Robinson, Illinois, hasNotableIndustryType, food industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableIndustryType Context triple: [Robinson, Illinois, hasNotableIndustryType, food industry]
-
A.
notableIndustry
chosen
Indicates that an entity is significantly recognized or prominent within a specified industry or sector.
-
B.
hasNotableCompany
Indicates that an entity is associated with or linked to a company that is considered notable or significant in some context.
-
C.
hasNoMajorIndustry
Indicates that the referenced place or entity does not possess any dominant or significant industrial sector.
-
D.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: April 27, 2026, 9:20 p.m.