Triple
T38274415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US Patent 821393 |
E1021903
|
entity |
| Predicate | typeOfInvention |
P24461
|
FINISHED |
| Object | mechanical invention |
—
|
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: mechanical invention | Statement: [US Patent 821393, typeOfInvention, mechanical invention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfInvention Context triple: [US Patent 821393, typeOfInvention, mechanical invention]
-
A.
inventionType
chosen
Indicates the specific category or kind of invention that characterizes the relationship between an invention and its type.
-
B.
invention
Indicates that one entity is the creator or originator of another entity, typically a device, method, or idea.
-
C.
usedInventionOf
Indicates that one entity made use of, applied, or implemented the invention created by another entity.
-
D.
inventionName
Indicates that the predicate specifies the name or title assigned to a particular invention.
-
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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.