Triple
T24758608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LV907 |
E619363
|
entity |
| Predicate | hasNoseArtTheme |
P68894
|
FINISHED |
| Object | superstitious motif of Friday the 13th |
—
|
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: superstitious motif of Friday the 13th | Statement: [LV907, hasNoseArtTheme, superstitious motif of Friday the 13th]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoseArtTheme Context triple: [LV907, hasNoseArtTheme, superstitious motif of Friday the 13th]
-
A.
hasCoverArtTheme
Indicates that an item’s cover art visually represents or is characterized by a particular theme or motif.
-
B.
hasArtFeature
chosen
Indicates that an entity possesses or is characterized by a particular artistic attribute, element, or stylistic feature.
-
C.
artisticTheme
Indicates the central artistic subject, concept, or motif that characterizes or is expressed by a creative work.
-
D.
hasSayingTheme
Indicates that a saying, proverb, or quoted expression is about or centers on a particular theme or subject.
-
E.
hasOfficialArtwork
Indicates that an entity is associated with an officially sanctioned piece of artwork representing it.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 4:26 a.m.