Triple
T7312104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gleason family |
E168114
|
entity |
| Predicate | knownForInnovationIn |
P16245
|
FINISHED |
| Object | gear-cutting technology |
—
|
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: gear-cutting technology | Statement: [Gleason family, knownForInnovationIn, gear-cutting technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForInnovationIn Context triple: [Gleason family, knownForInnovationIn, gear-cutting technology]
-
A.
notableInventor
Indicates that the subject is a well-known or historically significant inventor of the object.
-
B.
innovationFrom
Indicates that something originates, arises, or is derived as an innovation from a particular source or prior 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.
innovationArea
chosen
Indicates the thematic or domain-specific field in which an innovation is focused or applied.
-
E.
notableLaureatesInclude
Indicates that a group, institution, or award has among its distinguished recipients or members certain specified laureates.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ec00fef081909cb9768a70cabd80 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.