Triple
T6854544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goya champuru |
E158104
|
entity |
| Predicate | oftenEatenWith |
P14740
|
FINISHED |
| Object | rice |
—
|
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: rice | Statement: [Goya champuru, oftenEatenWith, rice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenEatenWith Context triple: [Goya champuru, oftenEatenWith, rice]
-
A.
typicallyEatenAt
Indicates that something is most commonly or customarily eaten during a particular time, event, or context.
-
B.
typicalFoodPairing
chosen
Indicates that one food item is commonly served, consumed, or matched together with another as a customary or complementary pairing.
-
C.
eatenOnOccasion
Indicates that one entity is consumed or eaten by another only at certain times or under specific circumstances, rather than regularly or habitually.
-
D.
sharesCuisineWith
Indicates that two entities offer or are associated with the same type or style of cuisine.
-
E.
usuallyAccompaniedBy
Indicates that one entity is commonly or habitually found together with, or occurs in the presence of, 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d851321481908c49c2c949359703 |
completed | March 27, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69c6d0a12834819097d7e6c0b823745e |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:20 p.m.