Triple
T30466460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ballad of Jesse James |
E775153
|
entity |
| Predicate | mythologizes |
P54696
|
FINISHED |
| Object | Jesse James |
—
|
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: Jesse James | Statement: [The Ballad of Jesse James, mythologizes, Jesse James]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mythologizes Context triple: [The Ballad of Jesse James, mythologizes, Jesse James]
-
A.
mythologized
chosen
Indicates that one entity has been turned into or treated as a mythic, legendary, or highly idealized figure or story by another.
-
B.
usesMythOf
Indicates that one entity employs or invokes a myth or mythical narrative about another entity as part of its actions, explanations, or representations.
-
C.
mythologicalCapital
Indicates that a location serves as the principal or central city associated with a particular mythology or pantheon.
-
D.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
E.
mythVariant
Indicates that one mythological narrative is a version, retelling, or alternative form of another myth.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686f3c8348190b5fea0c6fbeae253 |
completed | May 2, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:11 p.m.