Triple
T9818662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dharmanagar |
E238470
|
entity |
| Predicate | hasLocalMarkets |
P2714
|
FINISHED |
| Object | wholesale markets |
—
|
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: wholesale markets | Statement: [Dharmanagar, hasLocalMarkets, wholesale markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalMarkets Context triple: [Dharmanagar, hasLocalMarkets, wholesale markets]
-
A.
hasRetailMarkets
Indicates that an entity operates, hosts, or is associated with one or more retail markets where goods or services are sold to consumers.
-
B.
hasMarket
chosen
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
C.
hasMarketingRegion
Indicates that an entity is associated with or assigned to a specific marketing region for targeting, management, or analysis purposes.
-
D.
marketsIn
Indicates that one entity promotes, sells, or offers another entity’s products or services within a particular market or geographic area.
-
E.
hasMarketStatus
Indicates the current commercial or trading condition of an entity, such as whether it is active, suspended, listed, or delisted in a market.
- 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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb2f5bfa481908a2d2cb3f3d7d585 |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:31 p.m.