Triple
T31657678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low Shoulder |
E807900
|
entity |
| Predicate | frontmanPortrayedBy |
P172966
|
FINISHED |
| Object | Adam Brody |
—
|
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: Adam Brody | Statement: [Low Shoulder, frontmanPortrayedBy, Adam Brody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontmanPortrayedBy Context triple: [Low Shoulder, frontmanPortrayedBy, Adam Brody]
-
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.
frontmanCauseOfDeath
Indicates the cause or circumstances of death of the frontman of a group or band.
-
E.
isCoFrontmanOf
Indicates that two or more individuals share the role of lead performer or front-facing representative in the same band, group, or act.
- F. None of above. chosen
Provenance (4 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b2d9aad88190a445f8f591cb19fc |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: April 30, 2026, 10:56 p.m.