Triple
T26841410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In the Groove |
E675785
|
entity |
| Predicate | hasReissueTitle |
P196207
|
FINISHED |
| Object | I Heard It Through the Grapevine! |
—
|
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: I Heard It Through the Grapevine! | Statement: [In the Groove, hasReissueTitle, I Heard It Through the Grapevine!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReissueTitle Context triple: [In the Groove, hasReissueTitle, I Heard It Through the Grapevine!]
-
A.
hasReissueProgram
Indicates that an entity offers a program or process for issuing replacements or updated versions of something previously provided.
-
B.
wasReissued
Indicates that an item, such as a document or edition, has been issued again after its original release.
-
C.
hasReissuePublisher
Indicates that an entity has been republished or reissued by a specified publisher.
-
D.
hasReissueModel
Indicates that an entity has a specific model or version that serves as its reissued or updated form.
-
E.
hasSubsequentReissue
Indicates that one entity is a later reissued version that follows another entity in sequence.
- F. None of above. chosen
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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
| PDg | Predicate description generation | batch_69fe1639613c8190aaf1b4c8e2d861ba |
completed | May 8, 2026, 4:58 p.m. |
Created at: April 27, 2026, 5:08 a.m.