Triple
T29915962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantonese stir-fried shrimp with eggs |
E759795
|
entity |
| Predicate | typicalSide |
P55511
|
FINISHED |
| Object | steamed 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: steamed rice | Statement: [Cantonese stir-fried shrimp with eggs, typicalSide, steamed rice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSide Context triple: [Cantonese stir-fried shrimp with eggs, typicalSide, steamed rice]
-
A.
typicalVenueSide
Indicates the usual or standard side or location within a venue where something (such as an activity, feature, or participant) is typically situated or occurs.
-
B.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
sideType
Indicates the specific role or position an entity occupies within a two-sided or multi-sided relationship (e.g., buyer vs. seller, left vs. right side).
-
D.
hasTypicalSide
Indicates that one entity is the usual or characteristic side (e.g., lateral aspect) associated with another entity.
-
E.
servesSide
chosen
Indicates that one entity is provided or presented as an accompanying side item to another primary 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a03142a3a7081909bcfb683b44e2217 |
completed | May 12, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_6a031400af808190a72abf095e96c151 |
completed | May 12, 2026, 11:50 a.m. |
Created at: April 29, 2026, 6:12 p.m.