Triple
T12349978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tracks of My Tears |
E294456
|
entity |
| Predicate | hasLabelImprint |
P49200
|
FINISHED |
| Object | Tamla 54118 |
—
|
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: Tamla 54118 | Statement: [The Tracks of My Tears, hasLabelImprint, Tamla 54118]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLabelImprint Context triple: [The Tracks of My Tears, hasLabelImprint, Tamla 54118]
-
A.
associatedLabelOrImprint
chosen
Indicates a relationship where one entity serves as the label or imprint formally linked to, or published in association with, another entity.
-
B.
hadImprint
Indicates that one entity bears or once bore a physical or symbolic mark, stamp, or impression produced by another entity.
-
C.
hasSubImprint
Indicates that one imprint functions as a subordinate or subsidiary imprint under another imprint.
-
D.
hasImprintStyle
Indicates that one entity bears or exhibits a particular style, pattern, or form of imprint associated with another entity.
-
E.
hasImprintStatus
Indicates that an entity has a particular imprint-related status or condition assigned to it.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7cbff08190849cd2aec4ce3243 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.