Triple
T25142665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phillauri |
E629843
|
entity |
| Predicate | genreBlend |
P85590
|
FINISHED |
| Object | drama |
—
|
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: drama | Statement: [Phillauri, genreBlend, drama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreBlend Context triple: [Phillauri, genreBlend, drama]
-
A.
musicFusionOf
Indicates a relationship where one musical work, style, or element is created by combining or blending two or more distinct musical sources or genres.
-
B.
genreShift
Indicates a change in the type or style of content, such as switching from one genre to another within a work or between works.
-
C.
isOnGenreBlendingAlbum
Indicates that something (typically a song or track) appears on an album characterized by blending or combining multiple musical genres.
-
D.
genreDiversity
Indicates the extent to which an entity involves, includes, or spans multiple distinct genres rather than being confined to a single genre.
-
E.
combinesGenre
chosen
Indicates that an entity integrates or merges multiple genres into a single combined form or work.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:29 a.m.