Triple
T8623091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | chikhirtma |
E204214
|
entity |
| Predicate | hasServingContext |
P77271
|
FINISHED |
| Object | home cooking |
—
|
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: home cooking | Statement: [chikhirtma, hasServingContext, home cooking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServingContext Context triple: [chikhirtma, hasServingContext, home cooking]
-
A.
isServed
Indicates that one entity provides or delivers a service, product, or assistance to another entity.
-
B.
hasLaunchContext
Indicates that an entity is associated with a specific situation, environment, or set of conditions under which it is initiated or launched.
-
C.
hasPrimaryStateServed
Indicates that an entity has served or operated primarily within a specified state or state-level jurisdiction.
-
D.
hasServingCustom
chosen
Indicates that an entity follows or applies a particular custom, style, or convention in how something (such as food, drink, or service) is served.
-
E.
hasStateServed
Indicates that an entity has served in, been employed by, or otherwise held a role within a particular state or governmental jurisdiction.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:26 p.m.