Triple
T36141519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shine Over Babylon |
E1045317
|
entity |
| Predicate | hasFemaleSongwriter |
P191615
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Shine Over Babylon, hasFemaleSongwriter, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFemaleSongwriter Context triple: [Shine Over Babylon, hasFemaleSongwriter, yes]
-
A.
hasFemaleArtists
Indicates that the subject includes, features, or is associated with one or more female artists.
-
B.
hasPrimarySongwriter
Indicates that one entity serves as the main or principal songwriter responsible for creating the songs associated with another entity.
-
C.
hasSingerSongwriter
Indicates that an entity is associated with a person who both sings and writes the songs for it.
-
D.
notableSongwriterOn
Indicates that one entity is recognized as a notable songwriter contributing to or associated with another entity (such as a musical work or recording).
-
E.
hasWrittenSongsFor
Indicates that one entity has composed songs specifically intended to be performed, recorded, or used by another entity.
- F. None of above. chosen
Provenance (4 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.