Triple
T36328199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woman’s Gotta Have It |
E894551
|
entity |
| Predicate | hasPerformerVersion |
P95695
|
FINISHED |
| Object | Bobby Womack studio version |
—
|
LITERAL FINISHED |
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: Bobby Womack studio version | Statement: [Woman’s Gotta Have It, hasPerformerVersion, Bobby Womack studio version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerVersion Context triple: [Woman’s Gotta Have It, hasPerformerVersion, Bobby Womack studio version]
-
A.
hasVersionFor
Indicates that one entity serves as a specific version or variant tailored for another entity.
-
B.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
C.
hasChildVersionOfSinger
Indicates that one entity is a child version or younger incarnation of a singer represented by another entity.
-
D.
hasInstrumentVersion
Indicates that an entity is associated with a specific version or variant of an instrument used in its creation, performance, or measurement.
-
E.
hasCoverVersionPerformer
chosen
Indicates that an entity is the performer of a cover version of another entity’s original work.
- 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_69f76e4dcf088190a6c3216c209cab52 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
Created at: May 3, 2026, 4:09 p.m.