Triple
T35543425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Beans and Rice |
E1027126
|
entity |
| Predicate | canBeMadeAs |
P2463
|
FINISHED |
| Object | vegetarian version |
—
|
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: vegetarian version | Statement: [Red Beans and Rice, canBeMadeAs, vegetarian version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeMadeAs Context triple: [Red Beans and Rice, canBeMadeAs, vegetarian version]
-
A.
madeWith
Indicates that one entity is created, produced, or constructed using another entity as a material, ingredient, or component.
-
B.
canMake
Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
-
C.
usesMake
Indicates that one entity employs, applies, or utilizes another entity as a means, tool, or method to achieve some purpose.
-
D.
craftable
Indicates that one entity can be created, assembled, or produced from other entities or resources, typically through a defined crafting process.
-
E.
canBe
chosen
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
- 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_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 3, 2026, 4:04 p.m.