Triple
T625457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Tundra |
E15807
|
entity |
| Predicate | manufacturerReputation |
P17845
|
FINISHED |
| Object | Toyota reliability |
—
|
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: Toyota reliability | Statement: [Toyota Tundra, manufacturerReputation, Toyota reliability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manufacturerReputation Context triple: [Toyota Tundra, manufacturerReputation, Toyota reliability]
-
A.
parentBrand
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
-
B.
manufacturedBy
Indicates that an item or product is produced or created by a specific manufacturer or maker.
-
C.
usedByManufacturer
Indicates that a manufacturer makes use of a particular resource, component, method, or tool in its production or operational processes.
-
D.
relatedBrand
Indicates a relationship where one brand is associated with, connected to, or otherwise related to another brand.
-
E.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e574444819087999404f3e3ffd9 |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49d0069d0819087c83b608f6fc053 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49e2107548190af0c1d67cfa475d1 |
completed | March 1, 2026, 8:14 p.m. |
Created at: March 1, 2026, 7:35 p.m.