Triple
T27949800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folklore era |
E703390
|
entity |
| Predicate | triggeredByReleaseOf |
P163072
|
FINISHED |
| Object | folklore (album) |
—
|
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: folklore (album) | Statement: [Folklore era, triggeredByReleaseOf, folklore (album)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggeredByReleaseOf Context triple: [Folklore era, triggeredByReleaseOf, folklore (album)]
-
A.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
B.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
C.
isReleasedInResponseTo
chosen
Indicates that an action, statement, or item is issued or made available as a direct reaction to a specific event, condition, or stimulus.
-
D.
releasedInsteadOf
Indicates that one entity was released in place of, or as a substitute for, another entity that was not released.
-
E.
triggeredFrom
Indicates that one event, action, or process was initiated or caused as a result of another specific event, action, or process.
- 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_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:24 p.m.