Triple
T5023358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor Willis |
E112909
|
entity |
| Predicate | performedCharacter |
P47022
|
FINISHED |
| Object | policeman persona in Village People |
—
|
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: policeman persona in Village People | Statement: [Victor Willis, performedCharacter, policeman persona in Village People]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedCharacter Context triple: [Victor Willis, performedCharacter, policeman persona in Village People]
-
A.
characterPerformer
chosen
Indicates that a performer portrays or voices a particular character in a work.
-
B.
originalPerformerCharacter
Indicates that a performer is the first or primary actor to portray a particular character in a work.
-
C.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
D.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
E.
originallyPerformedByCharacter
Indicates that an action, work, or role was first carried out or portrayed by a particular character.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73670578819099a56112950708a8 |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.