Triple
T18356707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parlophone PMC 1206 (mono) |
E439814
|
entity |
| Predicate | hasMatrixNumber |
P130788
|
FINISHED |
| Object | XEX 447 (side 1, typical UK mono pressing) |
—
|
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: XEX 447 (side 1, typical UK mono pressing) | Statement: [Parlophone PMC 1206 (mono), hasMatrixNumber, XEX 447 (side 1, typical UK mono pressing)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatrixNumber Context triple: [Parlophone PMC 1206 (mono), hasMatrixNumber, XEX 447 (side 1, typical UK mono pressing)]
-
A.
hasMatrixSize
Indicates that an entity (such as a matrix or array) has a specific dimensional size, typically expressed as its number of rows and columns.
-
B.
hasMatrixType
Indicates that an entity is associated with or characterized by a specific type or category of matrix.
-
C.
hasCardNumber
Indicates that an entity is associated with, or assigned, a specific card number.
-
D.
hasBandNumber
Indicates that an entity is associated with a specific band identification number.
-
E.
hasLockNumber
Indicates that an entity is associated with a specific lock identified by a number.
- F. None of above. chosen
Provenance (4 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e516d776cc8190937d7e1d42a36a3b |
completed | April 19, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:37 a.m.