Triple
T28673765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snapshot |
E725803
|
entity |
| Predicate | isExpandedFrom |
P113385
|
FINISHED |
| Object | earlier short story concept by Brandon Sanderson |
—
|
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: earlier short story concept by Brandon Sanderson | Statement: [Snapshot, isExpandedFrom, earlier short story concept by Brandon Sanderson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExpandedFrom Context triple: [Snapshot, isExpandedFrom, earlier short story concept by Brandon Sanderson]
-
A.
wasExpandedIn
Indicates that something increased in size, scope, or extent during a specified time or event.
-
B.
wasExpanded
Indicates that something increased in size, scope, or extent compared to its previous state.
-
C.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
D.
expandsIn
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
-
E.
expansionFrom
chosen
Indicates that one entity results from or is derived through the enlargement, extension, or unfolding 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:05 a.m.