Triple
T33271764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul Food |
E851793
|
entity |
| Predicate | publicationCollectionType |
P218
|
FINISHED |
| Object | essay collection |
—
|
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: essay collection | Statement: [Soul Food, publicationCollectionType, essay collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationCollectionType Context triple: [Soul Food, publicationCollectionType, essay collection]
-
A.
publicationCollection
Indicates that one entity is a collection or grouping that contains or organizes multiple publication entities.
-
B.
publicationType
chosen
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
C.
publicationTypeOf
Indicates that one entity specifies the type or category of publication to which another publication entity belongs.
-
D.
publicationSeriesType
Indicates the specific kind or category of series to which a publication belongs (e.g., journal series, book series, report series).
-
E.
collectionPublication
Indicates that a collection has been formally published or made publicly available, typically through some publishing process or platform.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
Created at: May 1, 2026, 1:32 a.m.