Triple
T1200765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunger Strike |
E25774
|
entity |
| Predicate | includedOnCompilation |
P16605
|
FINISHED |
| Object | various grunge-era retrospectives |
—
|
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: various grunge-era retrospectives | Statement: [Hunger Strike, includedOnCompilation, various grunge-era retrospectives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedOnCompilation Context triple: [Hunger Strike, includedOnCompilation, various grunge-era retrospectives]
-
A.
compiledIn
Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
-
B.
isCompilationOf
Indicates that one entity is a collected or assembled version made up of multiple other entities.
-
C.
includedWith
chosen
Indicates that one entity is provided or packaged together as part of another entity.
-
D.
compilationType
Indicates the specific method or mode by which something is compiled or assembled into a final form.
-
E.
compiledUnder
Indicates that something (typically code or a program) was built or translated into executable form using a specific compiler, configuration, or compilation environment.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9ec3488190afe35af54efae5e9 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5ed2b88190aab992913957e1cf |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.