Triple
T37116226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APMC Market (Turbhe–Vashi) |
E919123
|
entity |
| Predicate | buyersType |
P809
|
FINISHED |
| Object | wholesalers |
—
|
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: wholesalers | Statement: [APMC Market (Turbhe–Vashi), buyersType, wholesalers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buyersType Context triple: [APMC Market (Turbhe–Vashi), buyersType, wholesalers]
-
A.
sellerType
Indicates the classification or category of the party acting as the seller in a transaction or relationship.
-
B.
targetBorrowers
Indicates that certain entities are the intended or eligible recipients of a loan or borrowing arrangement from another entity.
-
C.
customerType
chosen
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
D.
saleType
Indicates the specific category or method by which a sale is conducted or classified (e.g., retail, wholesale, auction).
-
E.
eligiblePurchasers
Indicates that certain entities are permitted or qualified to make a particular purchase under specified rules or conditions.
- 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.