Triple
T25007083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The White Road |
E625870
|
entity |
| Predicate | isStandaloneStory |
P92727
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The White Road, isStandaloneStory, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStandaloneStory Context triple: [The White Road, isStandaloneStory, true]
-
A.
hasStandaloneTales
Indicates that an entity includes or is associated with independent, self-contained stories that can be understood without relying on a larger narrative.
-
B.
isSideStoryTo
Indicates that one narrative work is a supplementary or tangential story that expands on, but is not central to, the main storyline of another work.
-
C.
isStoried
Indicates that something has a rich history, reputation, or legacy built up over time, often marked by notable events or traditions.
-
D.
isStandaloneWork
chosen
Indicates that a work exists independently and is not part of a larger series, collection, or multi-part work.
-
E.
isNarrativeDriven
Indicates that an entity’s primary structure or progression is guided by a storyline or plot rather than by mechanics, data, or other non-story elements.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44b12bd788190bc32bb8129c4550e |
completed | May 1, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:05 a.m.