Triple
T28413632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dame Edna’s Talk Show |
E719737
|
entity |
| Predicate | hasCentralCharacterTrait |
P37384
|
FINISHED |
| Object | flamboyant |
—
|
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: flamboyant | Statement: [Dame Edna’s Talk Show, hasCentralCharacterTrait, flamboyant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralCharacterTrait Context triple: [Dame Edna’s Talk Show, hasCentralCharacterTrait, flamboyant]
-
A.
hasSupportingCharacterTrait
Indicates that a supporting character possesses a particular trait, quality, or characteristic.
-
B.
hasMainPersonality
Indicates that one entity possesses or is characterized by a primary or dominant personality associated with another entity.
-
C.
protagonistCharacteristic
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
D.
hasNotableTraitInPlot
Indicates that a character or entity possesses a distinctive trait that plays a significant role within the narrative or plot.
-
E.
associatedCharacterTrait
chosen
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 1:28 a.m.