Triple
T35408980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Popstars (UK TV series) |
E1023448
|
entity |
| Predicate | alsoFeaturedGroup |
P82072
|
FINISHED |
| Object | Liberty X |
—
|
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: Liberty X | Statement: [Popstars (UK TV series), alsoFeaturedGroup, Liberty X]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoFeaturedGroup Context triple: [Popstars (UK TV series), alsoFeaturedGroup, Liberty X]
-
A.
alsoFeatured
chosen
Indicates that an entity appears in addition to another primary entity within the same context, work, or presentation.
-
B.
culturalGroupFeatured
Indicates that a particular cultural group is prominently highlighted, showcased, or given special attention in a context, event, or medium.
-
C.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
-
D.
featuresGroup
Indicates that an entity includes or is associated with a specific group as one of its features or components.
-
E.
participantGroup
Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79564e2348190ba2a1badfe33b995 |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.