Triple
T36252873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Callin' Baton Rouge |
E891846
|
entity |
| Predicate | popularInGenre |
P184813
|
FINISHED |
| Object | country music |
—
|
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: country music | Statement: [Callin' Baton Rouge, popularInGenre, country music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularInGenre Context triple: [Callin' Baton Rouge, popularInGenre, country music]
-
A.
isPopularInGenre
chosen
Indicates that an entity enjoys significant recognition, approval, or widespread appeal within a specified genre.
-
B.
cultPopularIn
Indicates that a particular cult has significant popularity or following within a specified region, community, or population.
-
C.
cultPopularFrom
Indicates that something has gained or exhibits cult popularity originating from a particular source, context, or group.
-
D.
popularFrom
Indicates that something gains or holds popularity starting from a specific time, source, or context.
-
E.
popularityContext
Indicates the situational or domain-specific setting in which something’s popularity or level of public favor is evaluated.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:09 p.m.