Triple
T23716637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Your Decision single cover |
E586023
|
entity |
| Predicate | usedForReleaseBy |
P153680
|
FINISHED |
| Object | Alice in Chains |
—
|
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: Alice in Chains | Statement: [Your Decision single cover, usedForReleaseBy, Alice in Chains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForReleaseBy Context triple: [Your Decision single cover, usedForReleaseBy, Alice in Chains]
-
A.
usedByFor
Indicates that one entity makes use of another entity for a specific purpose or function.
-
B.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
D.
releasedFor
Indicates that something has been made available or authorized for public use, distribution, or access.
-
E.
wasUsedBy
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b77c1de881909614988c7d0d1400 |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 6:54 p.m.