Triple
T28322365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banijay Group |
E717308
|
entity |
| Predicate | ownsFormat |
P164267
|
FINISHED |
| Object | Survivor |
—
|
NE NERFINISHED |
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: Survivor | Statement: [Banijay Group, ownsFormat, Survivor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownsFormat Context triple: [Banijay Group, ownsFormat, Survivor]
-
A.
playedFormat
Indicates that an entity (such as a game, show, or media content) is or was presented, delivered, or experienced in a particular format (such as digital, physical, live, or specific media type).
-
B.
homeAndAwayFormat
Indicates that a competition or matchup is structured so that each pair of opponents plays twice, once at each participant’s home venue and once away.
-
C.
usedFormat
Indicates that one entity employs or applies a particular format or representation in relation to another entity.
-
D.
homeRecord
Indicates the record or statistics associated with an entity’s performance or activity in its home context or location.
-
E.
ownsLine
Indicates that one entity has ownership or legal control over a particular line, such as a route, service line, or communication line.
- F. None of above. chosen
Provenance (4 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6492c10d08190a8dbfdb678697af2 |
completed | May 2, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 28, 2026, 12:25 a.m.