Triple
T316216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khinkali |
E7711
|
entity |
| Predicate | servedWith |
P11944
|
FINISHED |
| Object | freshly ground black pepper |
—
|
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: freshly ground black pepper | Statement: [Khinkali, servedWith, freshly ground black pepper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedWith Context triple: [Khinkali, servedWith, freshly ground black pepper]
-
A.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
B.
servesField
Indicates that one entity performs a service or function specifically for, or in support of, a particular field, domain, or area of activity.
-
C.
alsoServes
Indicates that an entity, in addition to its primary role or function, provides service or support to another specified entity or group.
-
D.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
E.
servedByLine
Indicates that a transportation stop, station, or location is provided service by a specific transit line.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea6462148190825acc57f6d2adaf |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e943f12c8190883854aeed974260 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea08878c8190a5e8a90f620a3888 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.