Triple
T22599374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saans |
E574769
|
entity |
| Predicate | hasRepriseOrAlternateVersion |
P21698
|
FINISHED |
| Object | Saans (reprise) |
—
|
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: Saans (reprise) | Statement: [Saans, hasRepriseOrAlternateVersion, Saans (reprise)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepriseOrAlternateVersion Context triple: [Saans, hasRepriseOrAlternateVersion, Saans (reprise)]
-
A.
hasReprise
chosen
Indicates that an action, theme, or element is repeated or returns after its initial occurrence.
-
B.
hasAlternativeArrangement
Indicates that one entity can be organized, configured, or structured in a different valid way as an alternative to its current or primary arrangement.
-
C.
hasAlternativeRadioVersionWith
Indicates that one audio track has a corresponding alternative version specifically edited or mixed for radio play.
-
D.
hasCoverVersions
Indicates that a musical work has one or more recorded versions performed or produced by artists other than the original creator.
-
E.
hasCoverVersionPerformer
Indicates that an entity is the performer of a cover version of another entity’s original work.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626b5f5481909a104088d1c96720 |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:50 p.m.