Triple
T24955801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spam |
E624468
|
entity |
| Predicate | hasServingState |
P162072
|
FINISHED |
| Object | ready-to-eat |
—
|
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: ready-to-eat | Statement: [Spam, hasServingState, ready-to-eat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServingState Context triple: [Spam, hasServingState, ready-to-eat]
-
A.
hasPrimaryStateServed
Indicates that an entity has served or operated primarily within a specified state or state-level jurisdiction.
-
B.
hasStateServed
Indicates that an entity has served in, been employed by, or otherwise held a role within a particular state or governmental jurisdiction.
-
C.
isServed
Indicates that one entity provides or delivers a service, product, or assistance to another entity.
-
D.
hasSecondaryStateServed
Indicates that an entity has served in a secondary (additional) state or jurisdiction beyond its primary one.
-
E.
hasServingCustom
Indicates that an entity follows or applies a particular custom, style, or convention in how something (such as food, drink, or service) is served.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 18, 2026, 5:57 a.m.