Triple
T32690239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thermo King |
E835836
|
entity |
| Predicate | inventionAssociatedWith |
P165145
|
FINISHED |
| Object | mobile mechanical refrigeration |
—
|
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: mobile mechanical refrigeration | Statement: [Thermo King, inventionAssociatedWith, mobile mechanical refrigeration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inventionAssociatedWith Context triple: [Thermo King, inventionAssociatedWith, mobile mechanical refrigeration]
-
A.
usedInventionOf
Indicates that one entity made use of, applied, or implemented the invention created by another entity.
-
B.
inventionUsedBy
chosen
Indicates that a particular invention is utilized or employed by a specified entity.
-
C.
wasInventedBy
Indicates that something (typically an object, concept, or process) was created or brought into existence by a particular inventor or originator.
-
D.
inventionUsedIn
Indicates that a particular invention is utilized or applied within a specific context, process, product, or activity.
-
E.
basedOnInventionOf
Indicates that something is derived from, developed using, or fundamentally relies on a particular invention.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c81937a88190be6a17c72c801a70 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:09 a.m.