Triple
T7674336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I'm a Celebrity...Get Me Out of Here! |
E173822
|
entity |
| Predicate | presenterRole |
P72070
|
FINISHED |
| Object | main show hosts |
—
|
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: main show hosts | Statement: [I'm a Celebrity...Get Me Out of Here!, presenterRole, main show hosts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presenterRole Context triple: [I'm a Celebrity...Get Me Out of Here!, presenterRole, main show hosts]
-
A.
presenterOccupation
chosen
Indicates that an entity serves in a specific professional role or job as a presenter.
-
B.
audienceRole
Indicates the role or function an entity has as part of an audience in relation to another entity or event.
-
C.
speakerRole
Indicates the functional role or capacity in which an entity is acting as a speaker within a communicative event.
-
D.
mediaRole
Indicates the specific function, capacity, or position an entity holds in relation to a media item (such as creator, editor, performer, or distributor).
-
E.
introducesSpeakerRole
Indicates that one entity performs the act of presenting or announcing another entity in a specific speaker role.
- 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4 p.m.