Triple
T25905472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Goat |
E652737
|
entity |
| Predicate | hasStarringPerformanceStyle |
P130631
|
FINISHED |
| Object | deadpan 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: deadpan physical comedy | Statement: [The Goat, hasStarringPerformanceStyle, deadpan physical comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStarringPerformanceStyle Context triple: [The Goat, hasStarringPerformanceStyle, deadpan physical comedy]
-
A.
hasPerformerCredit
Indicates that a performer is credited for their role or contribution in a specific work, event, or production.
-
B.
hasTheatricalStyle
chosen
Indicates that one entity possesses, exhibits, or is characterized by a particular theatrical style associated with another entity.
-
C.
starredActorWith
Indicates that one entity participated as an actor in a production together with another specified actor.
-
D.
hasStageCreditsIn
Indicates that an entity has performed or been credited for work in a particular stage production or theatrical show.
-
E.
airedStarringActor
Indicates that a specific airing of a program featured a particular actor in a starring role.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 22, 2026, 8:27 a.m.