Triple
T37256208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Cogswell |
E924133
|
entity |
| Predicate | rivalCompanyProductType |
P187674
|
FINISHED |
| Object | sprockets |
—
|
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: sprockets | Statement: [Mr. Cogswell, rivalCompanyProductType, sprockets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalCompanyProductType Context triple: [Mr. Cogswell, rivalCompanyProductType, sprockets]
-
A.
vendorProductOf
Indicates that a product is offered or supplied by a particular vendor.
-
B.
technologyComparableTo
Indicates that one technology can be meaningfully compared to another in terms of capability, performance, or relevant characteristics.
-
C.
competingPlatform
Indicates that two platforms operate in the same market or domain and vie against each other to attract the same users, customers, or resources.
-
D.
componentTypeProduced
Indicates that one entity produces or manufactures a specific type of component as an output of its activity or process.
-
E.
associatedCompanyMainProductLine
Indicates that a company’s primary or main line of products is linked or related to a specified product category or product line.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:15 p.m.