Triple
T16996261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BharatBenz |
E412321
|
entity |
| Predicate | manufacturingModel |
P126094
|
FINISHED |
| Object | localized production in 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: localized production in India | Statement: [BharatBenz, manufacturingModel, localized production in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manufacturingModel Context triple: [BharatBenz, manufacturingModel, localized production in India]
-
A.
producedModel
Indicates that one entity created, manufactured, or generated the other entity as a model or product.
-
B.
usesProductionModel
Indicates that one entity employs or relies on another entity as its primary or official production model in practice.
-
C.
equipmentTypeProduced
Indicates that an entity produces or manufactures a particular type or category of equipment.
-
D.
componentTypeProduced
Indicates that one entity produces or manufactures a specific type of component as an output of its activity or process.
-
E.
manufacturerType
Indicates the classification or category of a manufacturer based on its role, characteristics, or production type.
- F. None of above. chosen
Provenance (4 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d2879af081909665f9f838bcfbe7 |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e378e037c88190935d732e0f10d5d7 |
completed | April 18, 2026, 12:28 p.m. |
Created at: April 10, 2026, 5:32 a.m.