Triple
T22462636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Blue |
E555267
|
entity |
| Predicate | hasMarketPresenceIn |
P90076
|
FINISHED |
| Object | urban India |
—
|
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: urban India | Statement: [Imperial Blue, hasMarketPresenceIn, urban India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketPresenceIn Context triple: [Imperial Blue, hasMarketPresenceIn, urban India]
-
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.
hasBrandPresence
chosen
Indicates that an entity maintains an official or recognizable representation (such as branding, marketing, or products) within a particular context, location, or platform.
-
D.
hasMarketStatus
Indicates the current commercial or trading condition of an entity, such as whether it is active, suspended, listed, or delisted in a market.
-
E.
hasMarketIndex
Indicates that an entity is associated with, or tracked by, a specific market index.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b80983081908084947b2e31c9d4 |
completed | April 29, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.