Triple
T11232597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karintha |
E265860
|
entity |
| Predicate | associatedWorkForm |
P86785
|
FINISHED |
| Object | lyrical vignette |
—
|
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: lyrical vignette | Statement: [Karintha, associatedWorkForm, lyrical vignette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWorkForm Context triple: [Karintha, associatedWorkForm, lyrical vignette]
-
A.
associatedWork
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
-
B.
associatedWorkType
chosen
Indicates the type or category of work with which an entity is associated (e.g., publication, artwork, performance).
-
C.
associatedWithWorkOf
Indicates that one entity has a connection or involvement with the work, creation, or output produced by another entity.
-
D.
relatedForm
Indicates that one entity is an alternative or variant form of another, such as a different spelling, inflection, or closely related lexical form.
-
E.
formOfWork
Indicates that one creative work is a specific form, version, or expression of another related 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9026e1c81909456ac946bbba972 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfdf7a88190aae21572e57ef208 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.