Triple
T4206784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coq au vin |
E93800
|
entity |
| Predicate | requiresStep |
P9959
|
FINISHED |
| Object | browning the chicken |
—
|
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: browning the chicken | Statement: [Coq au vin, requiresStep, browning the chicken]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresStep Context triple: [Coq au vin, requiresStep, browning the chicken]
-
A.
mayRequireAdditionalStep
Indicates that performing one action, process, or condition can necessitate an extra step beyond the standard or initial sequence.
-
B.
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.
-
C.
requiresStatus
Indicates that one entity can only proceed, be valid, or be applied if another entity has a specified status or condition.
-
D.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
E.
requiresConfiguration
Indicates that one entity depends on another to be set up or configured before it can function or be used.
- 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:03 p.m.