Triple
T27205999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yours Truly |
E683865
|
entity |
| Predicate | producerOfSoundRecording |
P42897
|
FINISHED |
| Object | Natalie MacMaster |
—
|
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: Natalie MacMaster | Statement: [Yours Truly, producerOfSoundRecording, Natalie MacMaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producerOfSoundRecording Context triple: [Yours Truly, producerOfSoundRecording, Natalie MacMaster]
-
A.
producedRecording
Indicates that one entity served as the producer responsible for creating or overseeing the making of a particular recording.
-
B.
creditedProducer
Indicates that an entity is acknowledged as a producer in the official credits of a work or production.
-
C.
recordingEngineer
Indicates that one entity serves as the recording engineer responsible for capturing and managing the audio for another entity (such as a musical work, session, or performance).
-
D.
recordProducer
chosen
Indicates that one entity serves as the producer responsible for creating or overseeing the production of a recorded work associated with another entity.
-
E.
artistRecorded
Indicates that an artist has recorded a particular musical work, track, or album.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 27, 2026, 9:38 a.m.