Triple
T29238796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heart of Lothian |
E741260
|
entity |
| Predicate | labelCatalogNumber7inchUK |
P34455
|
FINISHED |
| Object | EMI MARIL 5 |
—
|
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: EMI MARIL 5 | Statement: [Heart of Lothian, labelCatalogNumber7inchUK, EMI MARIL 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelCatalogNumber7inchUK Context triple: [Heart of Lothian, labelCatalogNumber7inchUK, EMI MARIL 5]
-
A.
length7inchVersion
Indicates that one entity is a version or release of another whose length corresponds to a 7-inch format (typically referring to a 7-inch record or similar medium).
-
B.
labelCatalog
Indicates assigning or associating a descriptive label or identifier with a catalog entity or catalog entry.
-
C.
hasUKVersion
Indicates that an entity has a corresponding version or variant that is specific to the United Kingdom.
-
D.
recordLabelCatalogNumber
chosen
Indicates the catalog or identification number assigned to a release by a record label.
-
E.
keyCatalogueNumber
Indicates the catalog or reference number assigned to a key within a key collection or inventory system.
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 12:30 p.m.