Triple
T32735607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | When I Get My Hands on You |
E837070
|
entity |
| Predicate | isFromProject |
P175836
|
FINISHED |
| Object | The New Basement Tapes |
—
|
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: The New Basement Tapes | Statement: [When I Get My Hands on You, isFromProject, The New Basement Tapes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFromProject Context triple: [When I Get My Hands on You, isFromProject, The New Basement Tapes]
-
A.
isOnProject
Indicates that an entity is currently assigned to, involved with, or working on a particular project.
-
B.
isOnProjectBy
Indicates that an entity is assigned to or working on a project under the responsibility or authorship of another entity.
-
C.
isSisterProjectOf
Indicates that two projects are related and aligned in purpose or scope, typically operating in parallel under a common umbrella or organization.
-
D.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
E.
includedProject
Indicates that one project is contained within, or forms a part of, another project.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d749e7f081909c8196898c4191ad |
completed | May 3, 2026, 5:04 a.m. |
Created at: May 1, 2026, 1:12 a.m.