Triple
T21641214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Eastern cuisine |
E534090
|
entity |
| Predicate | commonCourse |
P145349
|
FINISHED |
| Object | appetizer |
—
|
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: appetizer | Statement: [Middle Eastern cuisine, commonCourse, appetizer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonCourse Context triple: [Middle Eastern cuisine, commonCourse, appetizer]
-
A.
typicalCourse
Indicates that one entity is a standard or commonly taken course associated with another entity, such as a program, curriculum, or field of study.
-
B.
commonlyTaughtWith
Indicates that two subjects or concepts are frequently taught together within the same course, lesson, or curriculum context.
-
C.
coursePar
Indicates that two entities (such as paths, lines, or trajectories) run alongside each other in the same general direction without intersecting.
-
D.
courseClass
Indicates that a particular course is classified as belonging to a specific academic class or category.
-
E.
course
Indicates that an entity is an academic class or unit of instruction offered within an educational program.
- F. None of above. chosen
Provenance (4 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef53917f3c81909e7f4074beecefd3 |
completed | April 27, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:35 p.m.