Triple
T35726321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divorce Court |
E1032624
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reality court show |
C21622
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: reality court show Context triple: [Divorce Court, instanceOf, reality court show]
-
A.
court show
chosen
A court show is a television program that dramatizes or reenacts legal disputes in a courtroom setting, typically featuring a judge, litigants, and sometimes a jury, to entertain and inform viewers about legal processes.
-
B.
reality competition show
A reality competition show is an unscripted television program in which real-life contestants compete in challenges or tasks for a prize, with their progress and interactions documented over the course of the series.
-
C.
court theatre
A court theatre is a performance venue, often within or closely associated with a royal or noble residence, where plays, music, and other entertainments are staged primarily for the enjoyment of the court and its guests.
-
D.
reality television participant
A reality television participant is an individual who appears as themselves in an unscripted or semi-scripted TV program, engaging in real-life situations, competitions, or social dynamics for entertainment and public exposure.
-
E.
dating show franchise
A dating show franchise is a recurring television or streaming series brand that produces multiple related programs or seasons centered on structured romantic matchmaking, often reusing formats, hosts, and branding across different regions or spin-offs.
- F. None of above.
Provenance (1 batch)
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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.