Triple
T35567694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hit Da Pavement |
E1027821
|
entity |
| Predicate | performerNameUsed |
P36847
|
FINISHED |
| Object | Snoopzilla |
—
|
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: Snoopzilla | Statement: [Hit Da Pavement, performerNameUsed, Snoopzilla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerNameUsed Context triple: [Hit Da Pavement, performerNameUsed, Snoopzilla]
-
A.
hasPerformerGivenName
Indicates that a performer is associated with a specific given (first) name.
-
B.
performerFullName
Indicates the complete name of the entity that performs an action or role in the described context.
-
C.
performerCreditedAs
chosen
Indicates that a performer is associated with a work under a specific credited name or alias.
-
D.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
E.
performerBirthName
Indicates the full name a performer was given at birth, as distinct from any stage or professional name they may use.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: May 3, 2026, 4:04 p.m.