Triple
T7384306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karelian pies |
E170341
|
entity |
| Predicate | requiresPreparationStep |
P47540
|
FINISHED |
| Object | rolling thin rye dough |
—
|
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: rolling thin rye dough | Statement: [Karelian pies, requiresPreparationStep, rolling thin rye dough]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPreparationStep Context triple: [Karelian pies, requiresPreparationStep, rolling thin rye dough]
-
A.
preparationRequirement
Indicates that one entity must be prepared, configured, or made ready as a necessary condition before another entity, action, or process can occur or be valid.
-
B.
mayRequireAdditionalStep
Indicates that performing one action, process, or condition can necessitate an extra step beyond the standard or initial sequence.
-
C.
preparationInvolved
chosen
Indicates that a particular preparation, process, or setup is involved in enabling or carrying out an action, event, or relationship.
-
D.
preparesFor
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
E.
requiresInitialization
Indicates that one entity cannot be correctly used or executed until a specific setup or initialization process has been completed.
- 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1efe1308190b96eefbff56140be |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:08 p.m.