Triple
T28206182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PoP! |
E717028
|
entity |
| Predicate | frontmanCharacter |
P48734
|
FINISHED |
| Object | Alex Fletcher |
—
|
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: Alex Fletcher | Statement: [PoP!, frontmanCharacter, Alex Fletcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontmanCharacter Context triple: [PoP!, frontmanCharacter, Alex Fletcher]
-
A.
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.
-
B.
isFrontmanOf
Indicates that a person serves as the lead singer or primary representative performer of a band or musical group.
-
C.
guestVocalistIsFrontmanOf
Indicates that the guest vocalist performing on a work is also the lead singer (frontman) of the referenced band or primary musical act.
-
D.
isCoFrontmanOf
Indicates that two or more individuals share the role of lead performer or front-facing representative in the same band, group, or act.
-
E.
frontPerson
chosen
Indicates that one entity serves as the primary representative, leader, or public face positioned at the forefront in relation to another entity.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 10:35 p.m.