Triple
T17044690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philipp Matthäus Hahn |
E413534
|
entity |
| Predicate | typeOfInventions |
P24461
|
FINISHED |
| Object | mechanical calculators |
—
|
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 calculators | Statement: [Philipp Matthäus Hahn, typeOfInventions, mechanical calculators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfInventions Context triple: [Philipp Matthäus Hahn, typeOfInventions, mechanical calculators]
-
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.
hasInnovationType
Indicates that an entity is associated with, or classified by, a specific type or category of innovation.
-
D.
hasInventionProperty
Indicates that an entity possesses a specific characteristic, attribute, or quality related to an invention.
-
E.
innovationFrom
Indicates that something originates, arises, or is derived as an innovation from a particular source or prior entity.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3da9c112c81908232dc6908d831cf |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.