Triple
T8272763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman cuisine |
E193467
|
entity |
| Predicate | servedInContext |
P20031
|
FINISHED |
| Object | imperial palace cuisine |
—
|
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: imperial palace cuisine | Statement: [Ottoman cuisine, servedInContext, imperial palace cuisine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedInContext Context triple: [Ottoman cuisine, servedInContext, imperial palace cuisine]
-
A.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
B.
emergedInContext
chosen
Indicates that something came into existence, became apparent, or developed within a specific situation, environment, or set of circumstances.
-
C.
servedWith
Indicates that one item is customarily presented, provided, or consumed together with another as an accompaniment or side.
-
D.
isRaisedInContextOf
Indicates that an entity is brought up, discussed, or introduced within a particular situational, thematic, or conversational context.
-
E.
served
Indicates that one entity provided a service, assistance, or role-based function to or for 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb798878988190a5f63c854aa070f2 |
completed | March 31, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69cb70a4525481909399d313a6247ace |
completed | March 31, 2026, 6:58 a.m. |
Created at: March 30, 2026, 5:50 p.m.