Triple
T33183143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sutlac |
E849388
|
entity |
| Predicate | isOftenEatenOn |
P53136
|
FINISHED |
| Object | religious holidays in Turkey |
—
|
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: religious holidays in Turkey | Statement: [Sutlac, isOftenEatenOn, religious holidays in Turkey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenEatenOn Context triple: [Sutlac, isOftenEatenOn, religious holidays in Turkey]
-
A.
isOftenEaten
Indicates that the subject is frequently consumed as food by some agent or group.
-
B.
isTypicallyEatenWith
Indicates that one item is commonly consumed together with another as part of the same eating occasion or dish.
-
C.
isEatenIn
Indicates that one entity (typically food) is consumed within the context, location, or occasion specified by another entity.
-
D.
isEatenFor
Indicates that one entity is consumed as food for the benefit, nourishment, or use of another entity.
-
E.
typicallyEatenAt
chosen
Indicates that something is most commonly or customarily eaten during a particular time, event, or context.
- 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_69f3495d06508190b0b7729982982cea |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:29 a.m.