Triple
T32702333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Idea |
E836170
|
entity |
| Predicate | stageActionFeature |
P175025
|
FINISHED |
| Object | physical comedy |
—
|
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: physical comedy | Statement: [Bad Idea, stageActionFeature, physical comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageActionFeature Context triple: [Bad Idea, stageActionFeature, physical comedy]
-
A.
stageAppearanceFeature
Indicates a characteristic or attribute that is present or displayed in an entity’s stage appearance.
-
B.
stageSystem
Indicates a relationship where a system is arranged, set up, or prepared in stages or on a particular stage for operation or presentation.
-
C.
stageElement
Indicates that one entity functions as a component or part within the structure or configuration of another entity.
-
D.
stageDirector
Indicates a relationship where one entity serves as the stage director responsible for overseeing and coordinating the staging of a performance involving another entity.
-
E.
stage
Indicates that an entity organizes, presents, or performs another entity (such as an event, show, or action) as a staged occurrence.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: May 1, 2026, 1:10 a.m.