Triple
T25491097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bigg Boss Telugu |
E638837
|
entity |
| Predicate | showFormatFeature |
P41649
|
FINISHED |
| Object | weekly tasks |
—
|
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: weekly tasks | Statement: [Bigg Boss Telugu, showFormatFeature, weekly tasks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showFormatFeature Context triple: [Bigg Boss Telugu, showFormatFeature, weekly tasks]
-
A.
showFormatRole
Indicates the role or function that an entity has in relation to the format of a show or presentation.
-
B.
featuresFormat
Indicates that something (such as a product, service, or medium) is presented, delivered, or made available in a particular format or configuration.
-
C.
displaysFeature
chosen
Indicates that one entity presents, shows, or makes visible a particular feature or characteristic of another entity.
-
D.
supportsDebugFormats
Indicates that one entity provides or is compatible with debugging data or formats used by another entity.
-
E.
includeFormat
Indicates that one entity contains or specifies the format or representation type of another entity.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7a6493481908fccf217f6296b95 |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 2:38 p.m.