Triple
T19179593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xeelee Sequence |
E469534
|
entity |
| Predicate | hasShortStoryCollections |
P129131
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Xeelee Sequence, hasShortStoryCollections, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShortStoryCollections Context triple: [Xeelee Sequence, hasShortStoryCollections, yes]
-
A.
hasFictionComponent
Indicates that something includes, contains, or is composed in part of a fictional element or work.
-
B.
hasStandaloneTales
chosen
Indicates that an entity includes or is associated with independent, self-contained stories that can be understood without relying on a larger narrative.
-
C.
publisherOfStories
Indicates that one entity serves as the publisher responsible for releasing or distributing the stories created by another entity.
-
D.
hasAssociatedWorkOfFiction
Indicates that an entity is linked to a related work of fiction, such as a novel, film, or story that is associated with it.
-
E.
appearsInShortStoryBy
Indicates that one entity is a character, element, or subject that appears within a short story authored by 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f61ae4108190b3715261cac2dd86 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.