Triple
T25092021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Dogs |
E628486
|
entity |
| Predicate | hasConcessionsFocusedOnHotDogs |
P17433
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Chicago Dogs, hasConcessionsFocusedOnHotDogs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConcessionsFocusedOnHotDogs Context triple: [Chicago Dogs, hasConcessionsFocusedOnHotDogs, yes]
-
A.
hasHotDogThemedPromotions
Indicates that an entity runs or features promotions specifically themed around hot dogs.
-
B.
hasConcessions
chosen
Indicates that one entity provides or contains concession facilities, services, or rights (such as food, drink, or merchandise sales) for another entity or within a given context.
-
C.
hasDiningFocus
Indicates that an entity is primarily oriented toward or specialized in dining-related activities, services, or experiences.
-
D.
concessionIncludes
Indicates that one concession contains, comprises, or encompasses another concession as a part or subset.
-
E.
concessionArea
Indicates that one entity is a designated concession area associated with or located within another entity (such as a venue, facility, or site).
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 18, 2026, 6:24 a.m.