Triple
T11824990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Block |
E281235
|
entity |
| Predicate | typicalContestants |
P82094
|
FINISHED |
| Object | Couples |
—
|
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: Couples | Statement: [The Block, typicalContestants, Couples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalContestants Context triple: [The Block, typicalContestants, Couples]
-
A.
featuresContestants
chosen
Indicates that something (such as an event, show, or competition) includes or presents certain individuals as contestants.
-
B.
featuresContestantsFrom
Indicates that something, typically a show or event, includes contestants originating from a specified source or group.
-
C.
typicalCandidate
Indicates that an entity is a standard or representative example of what is usually considered a candidate in a given context.
-
D.
contestantOn
Indicates that one entity participates as a competitor in a contest, show, or competition associated with another entity.
-
E.
typicalContributors
Indicates the entities that commonly or characteristically contribute to, or are responsible for, another entity or outcome.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5eb299481909de3c0e85628fbe4 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.