Triple
T27218108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I'm a Celebrity...Get Me Out of Here! NOW! |
E681193
|
entity |
| Predicate | targetShow |
P860
|
FINISHED |
| Object | I'm a Celebrity...Get Me Out of Here! |
—
|
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: I'm a Celebrity...Get Me Out of Here! | Statement: [I'm a Celebrity...Get Me Out of Here! NOW!, targetShow, I'm a Celebrity...Get Me Out of Here!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetShow Context triple: [I'm a Celebrity...Get Me Out of Here! NOW!, targetShow, I'm a Celebrity...Get Me Out of Here!]
-
A.
targetsShow
Indicates that one entity is the intended audience or focus of a particular show or presentation.
-
B.
target
chosen
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
C.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
D.
showsThat
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
-
E.
targetLook
Indicates that one entity directs its gaze or visual focus toward another entity as a target.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 9:42 a.m.