Triple
T18816761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betim plant, Minas Gerais, Brazil |
E460155
|
entity |
| Predicate | producesProductType |
P90900
|
FINISHED |
| Object | passenger cars |
—
|
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: passenger cars | Statement: [Betim plant, Minas Gerais, Brazil, producesProductType, passenger cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producesProductType Context triple: [Betim plant, Minas Gerais, Brazil, producesProductType, passenger cars]
-
A.
componentTypeProduced
Indicates that one entity produces or manufactures a specific type of component as an output of its activity or process.
-
B.
equipmentTypeProduced
Indicates that an entity produces or manufactures a particular type or category of equipment.
-
C.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an entity.
-
D.
typeOfProducts
chosen
Indicates the kinds or categories of products that are associated with or offered by an entity.
-
E.
producesFor
Indicates that one entity creates, manufactures, or generates something specifically intended for another entity’s use, benefit, or distribution.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a6b620248190afa21a6ce61e2cff |
completed | April 20, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:55 a.m.