Triple
T38290191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A New-England Folktale |
E1022337
|
entity |
| Predicate | appliesToWorkReleaseYear |
P201136
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [A New-England Folktale, appliesToWorkReleaseYear, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToWorkReleaseYear Context triple: [A New-England Folktale, appliesToWorkReleaseYear, 2015]
-
A.
isFromWorkReleaseYear
Indicates that something originates from or is associated with a specific work’s release year.
-
B.
basedInWorkReleaseYear
Indicates that an entity is based in, or derived from, a work that was released in a specified year.
-
C.
sampledWorkReleaseYear
Indicates the year in which the work being sampled was originally released.
-
D.
createdForWorkReleasedInYear
Indicates that something was created specifically for a work that was released in a particular year.
-
E.
parentWorkReleaseYear
Indicates the calendar year in which the parent work associated with an entity was originally released.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffcb5536d88190bfc2e00b854cacfb |
completed | May 10, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69ffc900c2a081909dea04aa60566923 |
completed | May 9, 2026, 11:53 p.m. |
| PDg | Predicate description generation | batch_69ffcb5428b88190b154776ebcbb81e1 |
completed | May 10, 2026, 12:03 a.m. |
Created at: May 3, 2026, 4:30 p.m.