Triple
T8938884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charisma Records |
E212845
|
entity |
| Predicate | catalogueFocus |
P53888
|
FINISHED |
| Object | album-oriented rock |
—
|
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: album-oriented rock | Statement: [Charisma Records, catalogueFocus, album-oriented rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueFocus Context triple: [Charisma Records, catalogueFocus, album-oriented rock]
-
A.
categoryFocus
chosen
Indicates that one entity is the primary subject, theme, or focal point within the broader category defined by the other entity.
-
B.
catalogueType
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
C.
artCollectionFocus
Indicates that an art collection is primarily centered around or devoted to a particular theme, style, period, subject, or type of artwork.
-
D.
cataloguePrefix
Indicates that one entity serves as the initial or leading segment of another entity’s catalogue identifier or listing code.
-
E.
catalogueSystem
Indicates a relationship where one entity serves as or belongs to a cataloging system that organizes, indexes, or classifies other entities.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66b7484481909e0d7610552f5386 |
completed | April 1, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:58 p.m.