Triple
T10559281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinner Roll trick |
E249171
|
entity |
| Predicate | innovationLevel |
P94678
|
FINISHED |
| Object | groundbreaking |
—
|
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: groundbreaking | Statement: [Dinner Roll trick, innovationLevel, groundbreaking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: innovationLevel Context triple: [Dinner Roll trick, innovationLevel, groundbreaking]
-
A.
innovation
Indicates the introduction or development of something new or significantly improved compared to existing methods, products, or ideas.
-
B.
hasInnovationType
Indicates that an entity is associated with, or classified by, a specific type or category of innovation.
-
C.
innovationArea
Indicates the thematic or domain-specific field in which an innovation is focused or applied.
-
D.
innovationFrom
Indicates that something originates, arises, or is derived as an innovation from a particular source or prior entity.
-
E.
usedInnovation
Indicates that one entity applied or implemented an innovation (such as a new idea, method, or technology) in relation to another entity or context.
- F. None of above. chosen
Provenance (4 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5271e65688190bcf7931373d87f94 |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
| PDg | Predicate description generation | batch_69d5270eca0481908573b698390c5b08 |
completed | April 7, 2026, 3:47 p.m. |
Created at: April 6, 2026, 12:35 p.m.