Triple
T2127553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yemeni American |
E46459
|
entity |
| Predicate | notableBusinessType |
P35312
|
FINISHED |
| Object | corner store |
—
|
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: corner store | Statement: [Yemeni American, notableBusinessType, corner store]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBusinessType Context triple: [Yemeni American, notableBusinessType, corner store]
-
A.
notableCommercial
Indicates that an entity is particularly well-known or significant in a commercial context, such as advertising, marketing, or business promotion.
-
B.
notableRegionOfBusiness
Indicates that a specified geographic region is a significant or primary area in which an entity conducts its business activities.
-
C.
notableIndustry
Indicates that an entity is significantly recognized or prominent within a specified industry or sector.
-
D.
notableEmployer
Indicates that an entity has been employed by, or has worked for, a particularly significant or noteworthy organization or individual.
-
E.
notableServiceType
Indicates that the subject is associated with a particular type or category of service that is especially notable or significant.
- F. None of above. chosen
Provenance (4 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb75033881909b16659fc73945ef |
completed | March 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb895d11881908345032595a679ba |
completed | March 7, 2026, 5:33 a.m. |
Created at: March 4, 2026, 7:44 p.m.