Triple
T10258542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johannes Gutenberg |
E240535
|
entity |
| Predicate | significantInvention |
P14207
|
FINISHED |
| Object | movable metal type |
—
|
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: movable metal type | Statement: [Johannes Gutenberg, significantInvention, movable metal type]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantInvention Context triple: [Johannes Gutenberg, significantInvention, movable metal type]
-
A.
invention
Indicates that one entity is the creator or originator of another entity, typically a device, method, or idea.
-
B.
inventionType
Indicates the specific category or kind of invention that characterizes the relationship between an invention and its type.
-
C.
notableInventor
chosen
Indicates that the subject is a well-known or historically significant inventor of the object.
-
D.
wasInventedBy
Indicates that something (typically an object, concept, or process) was created or brought into existence by a particular inventor or originator.
-
E.
hasInventionProperty
Indicates that an entity possesses a specific characteristic, attribute, or quality related to an 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2b5853081909cd0397e08a0f44d |
completed | April 7, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69d4d1edae6881909a65201b8e51ea0a |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:31 a.m.