Triple
T23641922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Idol (judge) |
E583922
|
entity |
| Predicate | hasRoleInProcess |
P65172
|
FINISHED |
| Object | talent selection |
—
|
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: talent selection | Statement: [Indian Idol (judge), hasRoleInProcess, talent selection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInProcess Context triple: [Indian Idol (judge), hasRoleInProcess, talent selection]
-
A.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
B.
hasRoleInWorkType
Indicates that an entity holds a specific role or function within a particular type or category of work.
-
C.
hasStageRole
Indicates that an entity performs or holds a specific role or character in a staged performance or theatrical production.
-
D.
hasLegalRole
Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
-
E.
hasProceduralRole
chosen
Indicates that an entity participates in a process or procedure by fulfilling a specific functional role within that process.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b28152108190972ac680cba986d7 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.