Triple
T35543417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Beans and Rice |
E1027126
|
entity |
| Predicate | usesPreparationStep |
P47540
|
FINISHED |
| Object | soaking beans |
—
|
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: soaking beans | Statement: [Red Beans and Rice, usesPreparationStep, soaking beans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPreparationStep Context triple: [Red Beans and Rice, usesPreparationStep, soaking beans]
-
A.
preparationInvolved
chosen
Indicates that a particular preparation, process, or setup is involved in enabling or carrying out an action, event, or relationship.
-
B.
preparationBegan
Indicates that the initial actions or processes required for something to be carried out or occur have started.
-
C.
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.
-
D.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
E.
preparesFor
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:04 p.m.