Triple
T16727457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maruti Suzuki |
E406498
|
entity |
| Predicate | salesNetworkType |
P71003
|
FINISHED |
| Object | Arena dealerships |
—
|
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: Arena dealerships | Statement: [Maruti Suzuki, salesNetworkType, Arena dealerships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: salesNetworkType Context triple: [Maruti Suzuki, salesNetworkType, Arena dealerships]
-
A.
tradeNetworkScope
Indicates the extent or boundaries within which trade relationships or exchanges are conducted or recognized.
-
B.
tradeNetwork
Indicates a relationship where entities are connected through the exchange of goods, services, or resources within an ongoing system of trade.
-
C.
supportedNetwork
Indicates that one entity (such as a device, service, or application) is compatible with, operates on, or is designed to work over a specified network or type of network.
-
D.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
E.
businessNetworkType
chosen
Indicates the category or nature of the business relationship or network that connects the involved entities.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38748f538819097de1fdee9b42f34 |
completed | April 18, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.