Triple
T28766272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myrina |
E726277
|
entity |
| Predicate | belongsToNarrativeGenre |
P62560
|
FINISHED |
| Object | mythic history |
—
|
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: mythic history | Statement: [Myrina, belongsToNarrativeGenre, mythic history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToNarrativeGenre Context triple: [Myrina, belongsToNarrativeGenre, mythic history]
-
A.
literaryGenreAssociated
Indicates that there is an association between an entity and a particular literary genre with which it is related or classified.
-
B.
hasGenreRelation
Indicates that there is an association between an entity and a specific genre, specifying the type or category it belongs to.
-
C.
belongsToWorkGenre
chosen
Indicates that a creative work is classified under or associated with a particular genre.
-
D.
associatedWithGenreElement
Indicates that something has a connection or linkage to a specific genre-related element (such as a motif, convention, or stylistic feature).
-
E.
hasGenreInFiction
Indicates that a work of fiction belongs to or is categorized under a specific literary 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 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 28, 2026, 6:13 a.m.