Triple
T29193032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The NeverEnding Story II: The Next Chapter |
E740042
|
entity |
| Predicate | hasFictionalItem |
P114832
|
FINISHED |
| Object | Auryn |
—
|
NE NERFINISHED |
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: Auryn | Statement: [The NeverEnding Story II: The Next Chapter, hasFictionalItem, Auryn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalItem Context triple: [The NeverEnding Story II: The Next Chapter, hasFictionalItem, Auryn]
-
A.
hasFictionalProduct
chosen
Indicates a relationship where one entity features, offers, or includes a product that exists only in fiction or an imagined context.
-
B.
hasFictionalProperty
Indicates that an entity possesses a property, attribute, or characteristic that exists only in a fictional or imaginary context.
-
C.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
D.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
-
E.
hasFictionalCollector
Indicates that an entity is associated with a fictional character who collects or curates it.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: April 28, 2026, 12:03 p.m.