Triple
T30774863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tales from the Neverending Story |
E783633
|
entity |
| Predicate | featuresNewStorylines |
P201804
|
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: [Tales from the Neverending Story, featuresNewStorylines, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresNewStorylines Context triple: [Tales from the Neverending Story, featuresNewStorylines, true]
-
A.
notableRecentStoryline
Indicates that there is a particularly significant or newsworthy recent sequence of events or developments involving the subject.
-
B.
currentStories
Indicates that certain stories are presently active, relevant, or ongoing in a given context or system.
-
C.
notableStory
Indicates that an entity is the subject or source of a story, account, or narrative that is considered notable or significant.
-
D.
featuresNewAreas
Indicates that something includes or introduces previously unavailable or unexplored sections, regions, or domains.
-
E.
storylinesInclude
Indicates that certain storylines are contained within, or form part of, a larger narrative or collection of narratives.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_6a00233d32bc8190bea60b09b46ee7bc |
completed | May 10, 2026, 6:18 a.m. |
Created at: April 29, 2026, 8:40 p.m.