Triple
T23830170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Rockin' Tonight |
E589489
|
entity |
| Predicate | laterHitFor |
P151241
|
FINISHED |
| Object | Wynonie Harris |
—
|
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: Wynonie Harris | Statement: [Good Rockin' Tonight, laterHitFor, Wynonie Harris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterHitFor Context triple: [Good Rockin' Tonight, laterHitFor, Wynonie Harris]
-
A.
hitOver
Indicates that one entity strikes or impacts another entity by moving over or across it.
-
B.
becameHitDuring
Indicates that something rose in popularity or success and turned into a hit during a specified time period or event.
-
C.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
D.
laterWithin
Indicates that one event or time point occurs later than another while still falling within a specified temporal interval or boundary.
-
E.
producedHitFor
chosen
Indicates that one entity created or contributed to a successful or popular work (a "hit") for another entity.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f5de508190bd6bb6d89b8952d5 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:04 p.m.