Triple
T1219349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dodge City, Kansas |
E26181
|
entity |
| Predicate | tourismSlogan |
P25952
|
FINISHED |
| Object | Get the Heck into Dodge |
—
|
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: Get the Heck into Dodge | Statement: [Dodge City, Kansas, tourismSlogan, Get the Heck into Dodge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourismSlogan Context triple: [Dodge City, Kansas, tourismSlogan, Get the Heck into Dodge]
-
A.
tourismRegion
Indicates that a place or area is designated or recognized as a tourism region associated with another geographic or administrative entity.
-
B.
touristRegionNickname
Indicates that a tourist region is known by a particular informal or colloquial nickname.
-
C.
sloganGivenBy
Indicates that a particular slogan is provided, coined, or assigned by a specific entity.
-
D.
tourismFrom
Indicates that tourists or visitor activity originates from one place and is directed toward another location.
-
E.
sloganUsedIn
Indicates that a particular slogan is employed or featured within a specific context, such as a campaign, advertisement, or organization.
- 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_69a4948331fc8190b531ac9bec71c491 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be1d55a08190a138b2411a7c4376 |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd3140688190ac6e24de157fd61e |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:46 p.m.