Triple
T30402543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Regan: Standing Up |
E773386
|
entity |
| Predicate | starsComedianKnownFor |
P169166
|
FINISHED |
| Object | clean observational humor |
—
|
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: clean observational humor | Statement: [Brian Regan: Standing Up, starsComedianKnownFor, clean observational humor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starsComedianKnownFor Context triple: [Brian Regan: Standing Up, starsComedianKnownFor, clean observational humor]
-
A.
comedian
Indicates that the subject performs comedy or is recognized for engaging in comedic entertainment.
-
B.
actorKnownFor
Indicates that an actor is widely recognized or notable for a particular work, role, or contribution.
-
C.
creatorKnownFor
Indicates that a creator is especially recognized or notable for a particular work, contribution, or achievement.
-
D.
partnerInComedyDuo
Indicates that two entities are partners together in a comedy duo act or performance team.
-
E.
knownForAct
Indicates that an entity is recognized or notable for performing a particular act or action.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6861bcab481908946ee2d27a187c8 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:03 p.m.