Triple
T28344593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whole Again |
E717913
|
entity |
| Predicate | originalLineupOnRecording |
P160279
|
FINISHED |
| Object | Liz McClarnon |
—
|
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: Liz McClarnon | Statement: [Whole Again, originalLineupOnRecording, Liz McClarnon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalLineupOnRecording Context triple: [Whole Again, originalLineupOnRecording, Liz McClarnon]
-
A.
originalPerformerLineup
Indicates that the subject is associated with the initial or first group of performers who originally performed an event, work, or production.
-
B.
firstRecordingPersonnel
Indicates the personnel who were involved in making the first recording of an entity.
-
C.
bandMemberOnRecording
Indicates that a person is a member of a band who performed on a specific recording.
-
D.
mainPerformerLineup
Indicates that the specified entity is part of the primary group of performers featured in a particular event or performance lineup.
-
E.
vocalistOnOriginalRecording
chosen
Indicates that the subject served as the vocalist on the original recording of the work or track.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: April 28, 2026, 12:42 a.m.