Triple
T23751979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valerius Flaccus |
E586993
|
entity |
| Predicate | mythologicalCharactersInWork |
P64143
|
FINISHED |
| Object | Jason |
—
|
NE NERFINISHED |
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: Jason | Statement: [Valerius Flaccus, mythologicalCharactersInWork, Jason]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mythologicalCharactersInWork Context triple: [Valerius Flaccus, mythologicalCharactersInWork, Jason]
-
A.
mythologicalFigureFeatured
chosen
Indicates that a mythological figure is prominently depicted, referenced, or plays a significant role within a given work, context, or medium.
-
B.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
C.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
D.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
E.
folkloreCharacter
Indicates that one entity is a character originating from the traditional stories, myths, or legends associated with the other 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcc289e08190a8036bb16dd0220a |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:13 p.m.