Triple
T31973730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock, Rock, Rock! |
E816385
|
entity |
| Predicate | singingVoiceForTuesdayWeld |
P168042
|
FINISHED |
| Object | Connie Francis |
—
|
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: Connie Francis | Statement: [Rock, Rock, Rock!, singingVoiceForTuesdayWeld, Connie Francis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singingVoiceForTuesdayWeld Context triple: [Rock, Rock, Rock!, singingVoiceForTuesdayWeld, Connie Francis]
-
A.
singsVoiceBy
Indicates that a singing performance is rendered using a particular voice or vocal part.
-
B.
singsTo
Indicates that one entity performs singing directed toward or for another entity.
-
C.
vowDay
Indicates the specific day on which a vow, promise, or solemn commitment is formally made or takes effect.
-
D.
vocalInterpretationOf
Indicates that one entity is a vocal performance or rendition that expresses, realizes, or interprets the content of another entity.
-
E.
providedVocalPerformanceFor
chosen
Indicates that one entity delivered or contributed a vocal performance in support of, or as part of, another entity’s work, event, or production.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b34303a88190b17cadc63ce00be3 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:10 a.m.