Triple
T30484688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soulfire (album) |
E775682
|
entity |
| Predicate | hasLeadTrack |
P102128
|
FINISHED |
| Object | Soulfire (title track) |
—
|
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: Soulfire (title track) | Statement: [Soulfire (album), hasLeadTrack, Soulfire (title track)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadTrack Context triple: [Soulfire (album), hasLeadTrack, Soulfire (title track)]
-
A.
isLeadTrackOf
chosen
Indicates that a track serves as the primary or featured track associated with a particular release, album, or recording project.
-
B.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
C.
hasTrackFeatures
Indicates that something possesses or is associated with specific track-related characteristics or attributes.
-
D.
hasLeadInSeries
Indicates that one entity serves as the primary or starring role in a series associated with another entity.
-
E.
hasLeader
Indicates that one entity serves as the leader or head of 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 29, 2026, 8:13 p.m.