Triple
T31729056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spear of Longinus |
E809804
|
entity |
| Predicate | genreOfNarratives |
P11858
|
FINISHED |
| Object | hagiographic legend |
—
|
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: hagiographic legend | Statement: [Spear of Longinus, genreOfNarratives, hagiographic legend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreOfNarratives Context triple: [Spear of Longinus, genreOfNarratives, hagiographic legend]
-
A.
narrativeType
chosen
Indicates the specific kind or category of narrative (e.g., genre, structural form, or storytelling mode) associated with an entity.
-
B.
fieldOfNarrative
Indicates that a narrative (such as a story, account, or discourse) is situated within or pertains to a particular field, domain, or area of knowledge or activity.
-
C.
fictionalGenre
Indicates that a work of fiction belongs to or is categorized under a particular narrative genre or style.
-
D.
literaryGenreOfWork
Indicates that a work belongs to or is classified under a particular literary genre.
-
E.
narrativeTradition
Indicates the storytelling customs, conventions, or patterns that shape how narratives are typically told within a particular culture, group, or context.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 30, 2026, 11:21 p.m.