Triple
T28430555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia CL 2350 |
E715115
|
entity |
| Predicate | catalogNumberIssuer |
P149576
|
FINISHED |
| Object | Columbia Records |
—
|
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: Columbia Records | Statement: [Columbia CL 2350, catalogNumberIssuer, Columbia Records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogNumberIssuer Context triple: [Columbia CL 2350, catalogNumberIssuer, Columbia Records]
-
A.
CUSIPIssuerName
Indicates the name of the entity that issues the financial instrument identified by a given CUSIP.
-
B.
codeIssuer
chosen
Indicates that an entity is the one that issues, generates, or assigns a particular code to another entity or resource.
-
C.
barNumberIssuer
Indicates that the subject is the entity that issues or assigns the bar number associated with the object.
-
D.
catalogNumberDDO
Indicates the identifier or catalog number assigned to an item within the DDO cataloging or documentation system.
-
E.
headquartersOfIssuer
Indicates the location that serves as the main headquarters of the issuing entity.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 1:39 a.m.