Triple
T18840811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnin' |
E460788
|
entity |
| Predicate | performerInstanceOf |
P20624
|
FINISHED |
| Object | singer |
—
|
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: singer | Statement: [Burnin', performerInstanceOf, singer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerInstanceOf Context triple: [Burnin', performerInstanceOf, singer]
-
A.
performerType
chosen
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
B.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
C.
performerDescribedAs
Indicates that a performer is characterized or referred to using a particular description, label, or role.
-
D.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
E.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8e8f57081909edbbcaf56189816 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.