Triple
T7414070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chanderi |
E171083
|
entity |
| Predicate | hasMarketReach |
P39897
|
FINISHED |
| Object | domestic Indian market |
—
|
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: domestic Indian market | Statement: [Chanderi, hasMarketReach, domestic Indian market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketReach Context triple: [Chanderi, hasMarketReach, domestic Indian market]
-
A.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
B.
hasMarketFocus
Indicates that an entity concentrates its business activities, products, or services on a particular market or customer segment.
-
C.
marketReach
chosen
Indicates the extent or breadth of audience, customers, or geographic areas that a product, service, or message successfully reaches in the market.
-
D.
hasMarketingChannel
Indicates that an entity utilizes or is associated with a particular marketing channel for promotion or communication.
-
E.
hasMarketingTarget
Indicates that an entity is aimed at or intended to appeal to a specific marketing audience or 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c509ac8190876f207267a33a3b |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.