Triple
T16499955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In Bloom |
E400774
|
entity |
| Predicate | labelCataloguedAs |
P107050
|
FINISHED |
| Object | fourth single from Nevermind |
—
|
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: fourth single from Nevermind | Statement: [In Bloom, labelCataloguedAs, fourth single from Nevermind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelCataloguedAs Context triple: [In Bloom, labelCataloguedAs, fourth single from Nevermind]
-
A.
labelCatalog
Indicates assigning or associating a descriptive label or identifier with a catalog entity or catalog entry.
-
B.
labelOf
Indicates that one entity serves as the name, tag, or identifying label assigned to another entity.
-
C.
labelCatalogType
Indicates that an entity is assigned a specific catalog type label, defining its classification within a cataloging system.
-
D.
labelIndication
Indicates that a label or designation is assigned to an entity to specify its indication, purpose, or intended use.
-
E.
catalogued as
chosen
Indicates that one entity has been recorded or registered under a specific identifier or entry within a catalog or systematic listing.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e35b96881908c9d339eea9e4314 |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.