Triple
T31617261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Men from Shiloh |
E806793
|
entity |
| Predicate | hasDistinctMusicalScoreFrom |
P101517
|
FINISHED |
| Object | The Virginian |
—
|
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: The Virginian | Statement: [The Men from Shiloh, hasDistinctMusicalScoreFrom, The Virginian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctMusicalScoreFrom Context triple: [The Men from Shiloh, hasDistinctMusicalScoreFrom, The Virginian]
-
A.
hasNoMusicalScore
Indicates that something lacks an associated musical score or written musical accompaniment.
-
B.
hasNotableMelodicSimilarityTo
Indicates that one musical piece shares a clearly recognizable and significant similarity in melody with another.
-
C.
notableWorkComposedWith
Indicates that a notable work was created using, in collaboration with, or through the involvement of a particular tool, medium, system, or co-creative entity.
-
D.
hasDifferentMusicFrom
chosen
Indicates that two entities have music that is not the same in style, content, or identity.
-
E.
hasMusicalComposer
Indicates that one entity serves as the musical composer responsible for creating the music associated with 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: April 30, 2026, 10:39 p.m.