Triple
T27949802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folklore era |
E703390
|
entity |
| Predicate | associatedReleaseDate |
P66105
|
FINISHED |
| Object | 2020-07-24 |
—
|
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: 2020-07-24 | Statement: [Folklore era, associatedReleaseDate, 2020-07-24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedReleaseDate Context triple: [Folklore era, associatedReleaseDate, 2020-07-24]
-
A.
alsoReleasedOn
Indicates that the same item (such as a work, product, or release) was made available on an additional platform, format, or medium besides its primary one.
-
B.
businessReleaseDate
Indicates the date on which a product, service, or offering is officially made available for business or commercial use.
-
C.
releasedAt
chosen
Indicates the time or date at which something (such as a product, work, or item) is made publicly available or officially launched.
-
D.
regionReleaseDate
Indicates the date on which something is released or becomes available in a specific geographic region.
-
E.
alphaReleaseDate
Indicates the date on which an entity was first released in its alpha (early testing) version.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a008e29f76881908e656dbbd7fceea3 |
completed | May 10, 2026, 1:54 p.m. |
| PD | Predicate disambiguation | batch_6a008dc01b308190bc26e69814692f82 |
completed | May 10, 2026, 1:53 p.m. |
Created at: April 27, 2026, 7:24 p.m.