Triple
T23561717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I'll Be Your Shelter |
E579256
|
entity |
| Predicate | chartSuccessFor |
P127099
|
FINISHED |
| Object | Taylor Dayne |
—
|
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: Taylor Dayne | Statement: [I'll Be Your Shelter, chartSuccessFor, Taylor Dayne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chartSuccessFor Context triple: [I'll Be Your Shelter, chartSuccessFor, Taylor Dayne]
-
A.
chartSuccessWith
Indicates a relationship where one entity measures, tracks, or visualizes the success or performance of another entity using charts or similar representations.
-
B.
chartSuccessInCountry
Indicates that something has achieved a measurable level of success on music or sales charts within a specified country.
-
C.
chartStatus
Indicates the current state or condition of a chart, such as whether it is active, updated, or in a particular workflow stage.
-
D.
hasChartSuccessWith
chosen
Indicates that an entity has achieved measurable success on music or performance charts in connection with another specified entity.
-
E.
chartSystem
Indicates a relationship where a system is represented, organized, or tracked using a chart or charting method.
- 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_69e245fe24588190888f3aec8407d8e3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af68cddc8190ab9d0b7ee1f157ed |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:20 p.m.