Triple
T24204326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Goes to Hollywood |
E600061
|
entity |
| Predicate | hasRealityTVFormatElement |
P56853
|
FINISHED |
| Object | unscripted situations |
—
|
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: unscripted situations | Statement: [New York Goes to Hollywood, hasRealityTVFormatElement, unscripted situations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRealityTVFormatElement Context triple: [New York Goes to Hollywood, hasRealityTVFormatElement, unscripted situations]
-
A.
hasRealityTVElement
chosen
Indicates that something includes characteristics, themes, or stylistic features commonly associated with reality television.
-
B.
hasRealityTVSeries
Indicates that an entity is the subject or focus of a reality television series.
-
C.
networkOfRealityShow
Indicates that a particular reality show is broadcast or produced by a specific television network.
-
D.
televisionFormat
Indicates the specific type or style of television program or production format associated with an entity.
-
E.
hasNotableShowFormat
Indicates that an entity is associated with a specific, noteworthy format or structure of a show or program.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca38c148190ae65cd692567d43d |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:37 p.m.