Triple
T27219301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fun House |
E681224
|
entity |
| Predicate | presenterStyle |
P13362
|
FINISHED |
| Object | high-energy hosting by Pat Sharp |
—
|
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: high-energy hosting by Pat Sharp | Statement: [Fun House, presenterStyle, high-energy hosting by Pat Sharp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presenterStyle Context triple: [Fun House, presenterStyle, high-energy hosting by Pat Sharp]
-
A.
performanceStyle
chosen
Indicates the manner or style in which an action, work, or performance is carried out or presented.
-
B.
presenterField
Indicates that an entity serves as the presenter or speaker associated with a particular field, session, or content item.
-
C.
presenterOccupation
Indicates that an entity serves in a specific professional role or job as a presenter.
-
D.
commentarialStyle
Indicates the manner or approach taken in writing or presenting commentary on a text, event, or subject.
-
E.
stylist
Indicates that one entity serves as a stylist for another, providing professional advice or services related to appearance, fashion, or design.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 9:42 a.m.