Triple
T33309027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I’ll Be Your Girl (single) |
E852817
|
entity |
| Predicate | performerPreviousRole |
P103658
|
FINISHED |
| Object | groupie |
—
|
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: groupie | Statement: [I’ll Be Your Girl (single), performerPreviousRole, groupie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerPreviousRole Context triple: [I’ll Be Your Girl (single), performerPreviousRole, groupie]
-
A.
portrayedByPreviousNotableRoleContext
Indicates that an entity is portrayed by an actor whose casting is informed by, or references, a previous notable role that actor played.
-
B.
previouslyPortrayedBy
Indicates that the subject entity was portrayed in the past by the specified actor or performer.
-
C.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
-
D.
roleInPerformanceHistory
chosen
Indicates the specific role or function an entity held within a particular performance, as recorded in a historical context.
-
E.
premiereRoleOfPerformer
Indicates that a given role is the debut or first significant performance role of a particular performer.
- 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 1, 2026, 1:33 a.m.