Triple
T16766477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nina’s Tragedies |
E407476
|
entity |
| Predicate | blendsElements |
P47548
|
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: [Nina’s Tragedies, blendsElements, drama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blendsElements Context triple: [Nina’s Tragedies, blendsElements, drama]
-
A.
mixesElementsOf
chosen
Indicates a relationship where one entity combines or blends components, features, or aspects of another entity or set of entities into a unified whole.
-
B.
usedInBlends
Indicates that something serves as an ingredient or component within one or more mixtures, combinations, or blends.
-
C.
hasBlendOfOldAndNew
Indicates that something combines or integrates both traditional/older elements and modern/newer elements into a single whole.
-
D.
mixesWith
Indicates that one entity is combined or blended together with another entity to form a mixture.
-
E.
usesElementsOf
Indicates that one entity incorporates, applies, or draws upon components, principles, or features derived from 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b0330d6081908ce99f14c70b90f2 |
completed | April 18, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.