Triple
T20593095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hugh Lloyd |
E505980
|
entity |
| Predicate | typeOfComedian |
P85537
|
FINISHED |
| Object | character comedian |
—
|
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: character comedian | Statement: [Hugh Lloyd, typeOfComedian, character comedian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfComedian Context triple: [Hugh Lloyd, typeOfComedian, character comedian]
-
A.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
B.
typeOfPublicFigure
Indicates the specific category or role of public figure that an entity is classified as (e.g., politician, celebrity, activist).
-
C.
entertainmentType
Indicates the kind or category of entertainment associated with an entity or event.
-
D.
comedicDynamicWith
Indicates a relationship in which two or more entities interact in a way that creates or supports comedic effect, timing, or contrast.
-
E.
typicalPerformerRoleType
chosen
Indicates the usual or characteristic role type that a performer commonly plays or is associated with in their performances.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a97d63cc8190853e052d5930470d |
completed | April 20, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.