Triple
T30083787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir John in Love |
E764544
|
entity |
| Predicate | hasFolkMusicInfluence |
P127455
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sir John in Love, hasFolkMusicInfluence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFolkMusicInfluence Context triple: [Sir John in Love, hasFolkMusicInfluence, true]
-
A.
hasFolkGenre
Indicates that something belongs to, is categorized under, or is associated with the folk music genre.
-
B.
hasHarmonyInfluence
Indicates that one entity exerts an effect on, shapes, or contributes to the harmonic characteristics or structure of another entity.
-
C.
hasRhythmInfluence
Indicates that one entity has influenced or shaped the rhythmic patterns, style, or timing characteristics of another entity.
-
D.
isFolkSongFrom
Indicates that a folk song originates from or is traditionally associated with a particular place, region, or culture.
-
E.
usesMusicalInfluence
chosen
Indicates that one entity draws upon, incorporates, or is guided by the musical style, ideas, or legacy of another entity in its own musical creation or expression.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 29, 2026, 7:03 p.m.