Triple
T38629241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Primitive Lover |
E937403
|
entity |
| Predicate | hasSilentScore |
P197788
|
FINISHED |
| Object | accompanied by live or compiled musical score at exhibition |
—
|
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: accompanied by live or compiled musical score at exhibition | Statement: [The Primitive Lover, hasSilentScore, accompanied by live or compiled musical score at exhibition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSilentScore Context triple: [The Primitive Lover, hasSilentScore, accompanied by live or compiled musical score at exhibition]
-
A.
isSilentWithMusic
Indicates that an entity remains quiet or produces no audible sound when music is playing.
-
B.
hasScoreBy
Indicates that one entity possesses or is associated with a score that was assigned, produced, or determined by another entity.
-
C.
hasScoreRecord
Indicates that an entity is associated with a specific score entry or scoring record.
-
D.
hasScoreAvailable
Indicates that a score or rating for the relevant entity is present and can be accessed.
-
E.
isScoreFor
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
| PDg | Predicate description generation | batch_69feaa477f7c81909382b3aa77e7e11c |
completed | May 9, 2026, 3:30 a.m. |
Created at: May 3, 2026, 4:32 p.m.