Triple
T2845803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurel, Mississippi |
E62579
|
entity |
| Predicate | hasTelevisionExposure |
P37618
|
FINISHED |
| Object | featured on HGTV |
—
|
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: featured on HGTV | Statement: [Laurel, Mississippi, hasTelevisionExposure, featured on HGTV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTelevisionExposure Context triple: [Laurel, Mississippi, hasTelevisionExposure, featured on HGTV]
-
A.
televisionExposureLevel
Indicates the degree or amount of exposure an entity has to television content.
-
B.
isTelevised
Indicates that an event, program, or activity is broadcast on television for public viewing.
-
C.
hasBroadcastCoverageIn
Indicates that a broadcast (such as a TV or radio program, channel, or signal) is available or transmitted within a specified geographic area or region.
-
D.
mediaExposure
chosen
Indicates the extent to which an entity is subjected to or receives attention from media channels such as television, radio, print, or online platforms.
-
E.
televisionWork
Indicates a relationship where a creative work is produced for, broadcast on, or primarily associated with television.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf3d00708190966a477fdd855f23 |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.