Triple
T29513237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skunk Anansie |
E748714
|
entity |
| Predicate | frontperson |
P48734
|
FINISHED |
| Object | Skin |
—
|
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: Skin | Statement: [Skunk Anansie, frontperson, Skin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontperson Context triple: [Skunk Anansie, frontperson, Skin]
-
A.
frontPerson
chosen
Indicates that one entity serves as the primary representative, leader, or public face positioned at the forefront in relation to another entity.
-
B.
frontmanStageName
Indicates that the specified stage name is used by the person who serves as the frontman (lead performer) of a musical group or band.
-
C.
hasFrontPerson
Indicates that an entity is represented, led, or fronted publicly by a specific person.
-
D.
guestVocalistIsFrontmanOf
Indicates that the guest vocalist performing on a work is also the lead singer (frontman) of the referenced band or primary musical act.
-
E.
front
Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 4:34 p.m.