Triple
T28667346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delapore |
E725617
|
entity |
| Predicate | storyOriginallyPublishedIn |
P99724
|
FINISHED |
| Object | Weird Tales |
—
|
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: Weird Tales | Statement: [Delapore, storyOriginallyPublishedIn, Weird Tales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyOriginallyPublishedIn Context triple: [Delapore, storyOriginallyPublishedIn, Weird Tales]
-
A.
hasOriginalStory
Indicates that one entity serves as the original narrative source or story upon which the other entity is based or derived.
-
B.
originallyPublishedBy
chosen
Indicates that one entity is the original publisher or issuing source responsible for first making another entity publicly available.
-
C.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
D.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
E.
originStoryIncludes
Indicates that an entity’s origin story contains, involves, or features the referenced element as a component or part of that backstory.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 5:01 a.m.