Triple
T24012872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schuyler, Knobloch & Overstreet |
E594584
|
entity |
| Predicate | writesSongsFor |
P44022
|
FINISHED |
| Object | other country artists |
—
|
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: other country artists | Statement: [Schuyler, Knobloch & Overstreet, writesSongsFor, other country artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writesSongsFor Context triple: [Schuyler, Knobloch & Overstreet, writesSongsFor, other country artists]
-
A.
writesLyricsIn
Indicates that an entity creates or composes song lyrics in a specified language or writing system.
-
B.
writesLyricsAbout
Indicates that one entity creates song lyrics whose subject or theme is another entity.
-
C.
hasWrittenSongsFor
chosen
Indicates that one entity has composed songs specifically intended to be performed, recorded, or used by another entity.
-
D.
hasWrittenLyricsFor
Indicates that one entity is the lyricist who has created the words for a song or musical work performed or associated with another entity.
-
E.
coSongwriter
Indicates that two or more entities collaborated in writing the same song.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d59ee0a08190ad1e1bc2dad1dda7 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:41 p.m.