Triple
T29007235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French press |
E736468
|
entity |
| Predicate | involvesStep |
P9959
|
FINISHED |
| Object | add coarsely ground coffee to carafe |
—
|
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: add coarsely ground coffee to carafe | Statement: [French press, involvesStep, add coarsely ground coffee to carafe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesStep Context triple: [French press, involvesStep, add coarsely ground coffee to carafe]
-
A.
hasStep
chosen
Indicates that one entity includes, is composed of, or is associated with a specific step or stage in a process involving another entity.
-
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.
hasStepsLeadingTo
Indicates that one location or object is connected to another by a set of steps or a staircase leading toward it.
-
D.
isStepToward
Indicates that one action, state, or condition serves as progress or a necessary move in the direction of achieving another.
-
E.
stepType
Indicates the specific kind or category of step an entity represents within a process or sequence.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 28, 2026, 9:39 a.m.