Triple
T31193878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Do |
E795258
|
entity |
| Predicate | hasMusicWriter |
P23999
|
FINISHED |
| Object | Paul McCartney |
—
|
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: Paul McCartney | Statement: [I Do, hasMusicWriter, Paul McCartney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicWriter Context triple: [I Do, hasMusicWriter, Paul McCartney]
-
A.
hasMusicalComposer
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
B.
hasPrimarySongwriter
chosen
Indicates that one entity serves as the main or principal songwriter responsible for creating the songs associated with another entity.
-
C.
containsSongWrittenBy
Indicates that an entity (such as an album, playlist, or collection) includes at least one song that was written by a specified creator or songwriter.
-
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.
hasWrittenSongsFor
Indicates that one entity has composed songs specifically intended to be performed, recorded, or used by 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 29, 2026, 9:09 p.m.