Triple
T29311146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Beatles remastered catalogue |
E743235
|
entity |
| Predicate | audioSource |
P41641
|
FINISHED |
| Object | original analogue master tapes |
—
|
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: original analogue master tapes | Statement: [The Beatles remastered catalogue, audioSource, original analogue master tapes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioSource Context triple: [The Beatles remastered catalogue, audioSource, original analogue master tapes]
-
A.
audioStreaming
Indicates that one entity is transmitting audio data in real time for another entity to receive or play back.
-
B.
audioStack
Indicates that one audio element is layered or queued on top of another within an ordered audio sequence or mix.
-
C.
audioApplication
Indicates that an entity is an application whose primary function involves processing, playing, recording, or otherwise handling audio content.
-
D.
audioChip
Indicates that one entity functions as, or contains, an audio processing chip in relation to another entity.
-
E.
usesAudioFrom
chosen
Indicates that one entity incorporates or relies on the audio content produced or provided by another 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 1:16 p.m.