Triple
T32553821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ha-Ha's clown agency |
E832041
|
entity |
| Predicate | employsCharacterType |
P180826
|
FINISHED |
| Object | struggling performers |
—
|
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: struggling performers | Statement: [Ha-Ha's clown agency, employsCharacterType, struggling performers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employsCharacterType Context triple: [Ha-Ha's clown agency, employsCharacterType, struggling performers]
-
A.
workCharacterType
Indicates that a work involves or features a character of a specified type or role.
-
B.
usesCharacter
Indicates that one entity employs, incorporates, or relies on a particular character (such as a symbol, letter, or persona) in its form, function, or representation.
-
C.
helpsCharacterType
Indicates that one character type provides assistance or support to another character type.
-
D.
usedForCharacterType
Indicates that something is intended to be used for, or is suitable for, a particular type of character.
-
E.
usesCharactersAs
Indicates that one entity employs or incorporates specific characters (such as letters, symbols, or glyphs) from another entity for its representation or functioning.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: May 1, 2026, 1:02 a.m.