Triple
T32214257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skolemization |
E822885
|
entity |
| Predicate | typicalStepIn |
P206229
|
FINISHED |
| Object | conversion to clausal normal form |
—
|
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: conversion to clausal normal form | Statement: [Skolemization, typicalStepIn, conversion to clausal normal form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStepIn Context triple: [Skolemization, typicalStepIn, conversion to clausal normal form]
-
A.
typicalStep
Indicates that an action, event, or sub-process is a standard or commonly occurring step within a larger process or procedure.
-
B.
stepping
Indicates that an entity is moving its foot or feet to take a step, often as part of walking or changing position.
-
C.
stepType
Indicates the specific kind or category of step an entity represents within a process or sequence.
-
D.
stepTakes
Indicates that one step directly follows or is taken after another step in a process or sequence.
-
E.
isStepToward
Indicates that one action, state, or condition serves as progress or a necessary move in the direction of achieving another.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:37 a.m.