Triple
T3316848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MICA Entertainment |
E69701
|
entity |
| Predicate | associatedWorkGenre |
P38924
|
FINISHED |
| Object | historical 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: historical drama | Statement: [MICA Entertainment, associatedWorkGenre, historical drama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWorkGenre Context triple: [MICA Entertainment, associatedWorkGenre, historical drama]
-
A.
workedOnGenre
Indicates that an entity (such as a person or organization) has done work related to a particular genre.
-
B.
basedOnWorkGenre
Indicates that one entity’s genre classification is derived from or determined by the genre of another work.
-
C.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
D.
genreOfAssociatedPerson
Indicates that a particular genre is associated with a given person, such as an artist, author, or performer.
-
E.
genreAssociatedWith
chosen
Indicates a relationship where a work, item, or entity is linked to or categorized under a particular genre.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb11230b881908f5b554323729cc5 |
completed | March 8, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.