Triple
T33680502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gone at Last |
E862882
|
entity |
| Predicate | featuredChoir |
P4009
|
FINISHED |
| Object | The Jessy Dixon Singers |
E862887
|
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: The Jessy Dixon Singers | Statement: [Gone at Last, featuredChoir, The Jessy Dixon Singers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredChoir Context triple: [Gone at Last, featuredChoir, The Jessy Dixon Singers]
-
A.
hasChoir
chosen
Indicates that an entity possesses, maintains, or is associated with a choir.
-
B.
notableChorale
Indicates that a subject is recognized for or associated with a significant or distinguished chorale work or composition.
-
C.
chorusFeature
Indicates that one entity participates in or is highlighted within the chorus section of another entity, such as a song or musical piece.
-
D.
choirCompletion
Indicates that an entity has successfully finished or fulfilled its participation or required role in a choir-related activity or program.
-
E.
choirPosition
Indicates the relative placement or role an entity holds within a choir’s arrangement or structure.
- F. None of above.
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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a020ab9630c8190a55efd5704cc6043 |
completed | May 11, 2026, 4:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a363c90357c819091eb35fa9eb33780 |
completed | June 20, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_6a020800e2b88190a1a37e710d8c92bf |
completed | May 11, 2026, 4:46 p.m. |
Created at: May 1, 2026, 1:43 a.m.