Triple
T30357183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K. 173dB |
E772180
|
entity |
| Predicate | alternativeCatalogueNumberWith |
P84753
|
FINISHED |
| Object | K. 183 |
—
|
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: K. 183 | Statement: [K. 173dB, alternativeCatalogueNumberWith, K. 183]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeCatalogueNumberWith Context triple: [K. 173dB, alternativeCatalogueNumberWith, K. 183]
-
A.
alternativeCatalogNumber
chosen
Indicates that an entity is associated with an additional or substitute catalog number different from its primary catalog identifier.
-
B.
alternativeCataloguing
Indicates that an entity is catalogued or described using an additional or non-primary cataloguing system or scheme.
-
C.
recordLabelCatalogNumber
Indicates the catalog or identification number assigned to a release by a record label.
-
D.
hasAlternativeArrangement
Indicates that one entity can be organized, configured, or structured in a different valid way as an alternative to its current or primary arrangement.
-
E.
hasAlternativeNotation
Indicates that an entity can be represented or written in a different, equivalent form or notation.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 29, 2026, 7:57 p.m.