Triple
T24860326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Man in the Dark |
E622133
|
entity |
| Predicate | hasEmbeddedStory |
P131107
|
FINISHED |
| Object | alternate reality United States |
—
|
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: alternate reality United States | Statement: [Man in the Dark, hasEmbeddedStory, alternate reality United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmbeddedStory Context triple: [Man in the Dark, hasEmbeddedStory, alternate reality United States]
-
A.
numberOfEmbeddedStories
Indicates the count of stories that are embedded within a given item or context.
-
B.
hasSiblingInStory
Indicates that one character in a narrative has at least one sibling who also appears within the same story.
-
C.
isStoried
Indicates that something has a rich history, reputation, or legacy built up over time, often marked by notable events or traditions.
-
D.
hasVariantStoriesIn
chosen
Indicates that an entity has alternative or differing narrative versions that occur or are found within a specified context or source.
-
E.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:22 a.m.