Triple
T27032677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gelin |
E680963
|
entity |
| Predicate | featuredPerformanceBy |
P152890
|
FINISHED |
| Object | Hülya Koçyiğit |
—
|
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: Hülya Koçyiğit | Statement: [Gelin, featuredPerformanceBy, Hülya Koçyiğit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredPerformanceBy Context triple: [Gelin, featuredPerformanceBy, Hülya Koçyiğit]
-
A.
featuresSoloPerformancesBy
Indicates that the subject includes or showcases solo performances carried out by the specified performer or performers.
-
B.
featuredSongPerformancesFrom
Indicates that certain song performances are highlighted or prominently presented as originating from a particular source, event, or context.
-
C.
presentsPerformancesBy
Indicates that one entity organizes or stages performances that feature or are carried out by another entity.
-
D.
forPerformanceBy
Indicates that something is intended, designed, or suitable to be performed by a particular agent or performer.
-
E.
featuresOnScreenPerformer
chosen
Indicates that something (such as a work or production) includes a particular performer visibly appearing on screen.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 27, 2026, 7:14 a.m.