Triple
T30935274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strange Tales |
E788104
|
entity |
| Predicate | notableStoryType |
P207324
|
FINISHED |
| Object | Doctor Strange solo stories |
—
|
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: Doctor Strange solo stories | Statement: [Strange Tales, notableStoryType, Doctor Strange solo stories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStoryType Context triple: [Strange Tales, notableStoryType, Doctor Strange solo stories]
-
A.
notableStory
Indicates that an entity is the subject or source of a story, account, or narrative that is considered notable or significant.
-
B.
notableStorySubject
Indicates that the subject is a prominent or central topic, character, or element within a particular story or narrative.
-
C.
notableRecentStoryline
Indicates that there is a particularly significant or newsworthy recent sequence of events or developments involving the subject.
-
D.
notableStoryEvent
Indicates that an event plays a significant or memorable role within the narrative or storyline associated with the subject.
-
E.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
- F. None of above. chosen
Provenance (4 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 8:52 p.m.