Triple
T29963965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My People |
E761120
|
entity |
| Predicate | hasBeatProducedBy |
P151235
|
FINISHED |
| Object | Willy William |
—
|
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: Willy William | Statement: [My People, hasBeatProducedBy, Willy William]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeatProducedBy Context triple: [My People, hasBeatProducedBy, Willy William]
-
A.
hasBeat
Indicates that one entity has defeated or surpassed another in a competitive or comparative context.
-
B.
usesBeatFrom
chosen
Indicates that one entity employs or incorporates the rhythmic pattern, instrumental backing, or beat originally created for or associated with another entity.
-
C.
originalBeatPerformer
Indicates that an entity is the performer who first created or recorded the original beat or rhythmic backing for a work.
-
D.
hasBeatCount
Indicates that one entity specifies or is associated with the number of beats (e.g., rhythmic units or pulses) of another entity.
-
E.
hasNotableBeat
Indicates that an entity (such as a journalist or reporter) is professionally assigned to cover a specific topic, area, or subject as their primary reporting focus.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 29, 2026, 6:29 p.m.