Triple
T12032062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pure Shores |
E286435
|
entity |
| Predicate | isSignatureSongFor |
P7272
|
FINISHED |
| Object | All Saints |
E961020
|
NE 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: All Saints | Statement: [Pure Shores, isSignatureSongFor, All Saints]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: All Saints Context triple: [Pure Shores, isSignatureSongFor, All Saints]
-
A.
All Saints
All Saints is a Christian feast and collective title honoring all known and unknown saints of the Church.
-
B.
All Saints
chosen
All Saints are a British-Canadian girl group known for their smooth harmonies and late-1990s/early-2000s pop and R&B hits.
-
C.
Holy Angels
Holy Angels are celestial beings in Christian theology who serve as God’s messengers and protectors of humanity.
-
D.
Common of the Saints
Common of the Saints is a liturgical section containing standardized prayers, readings, and texts used for celebrating the feasts of various saints.
-
E.
All Angels
All Angels refers to the collective body of heavenly angels in Christian theology, often honored together in liturgy and church dedications.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9040724ec8190808f334013ddc6d6 |
completed | April 10, 2026, 2:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60a613054819082f7900a6ba8fbf8 |
completed | May 2, 2026, 2:29 p.m. |
Created at: April 8, 2026, 9:47 p.m.