Triple
T18730187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States retail industry |
E458013
|
entity |
| Predicate | includesSubsector |
P105701
|
FINISHED |
| Object | grocery retail |
—
|
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: grocery retail | Statement: [United States retail industry, includesSubsector, grocery retail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSubsector Context triple: [United States retail industry, includesSubsector, grocery retail]
-
A.
belongsToSubsector
chosen
Indicates that one entity is part of, or classified within, a more specific subsector of a broader sector or industry.
-
B.
isSectorSpecific
Indicates that something is tailored or restricted to a particular industry or sector rather than being generally applicable.
-
C.
hasGICSSubIndustry
Indicates that an entity is classified within a specific GICS (Global Industry Classification Standard) sub-industry category.
-
D.
coreSubsidiaryOf
Indicates that one entity is a primary or central subsidiary that is owned or controlled by another entity.
-
E.
hasMarketSector
Indicates that an entity operates within, is associated with, or belongs to a particular market sector or industry segment.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d778cf8819083500600b9ac0744 |
completed | April 20, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:50 a.m.