Triple
T33184791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alan Brady |
E849435
|
entity |
| Predicate | productionRoleInFiction |
P48208
|
FINISHED |
| Object | star of The Alan Brady Show |
—
|
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: star of The Alan Brady Show | Statement: [Alan Brady, productionRoleInFiction, star of The Alan Brady Show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionRoleInFiction Context triple: [Alan Brady, productionRoleInFiction, star of The Alan Brady Show]
-
A.
producerInFiction
Indicates that an entity serves as a producer (e.g., of a show, film, or other work) within a fictional context or narrative.
-
B.
creativeRole
Indicates that an entity holds a specific creative function or responsibility in relation to another entity, such as a work or project.
-
C.
fictionalUniverseRole
chosen
Indicates the role or function an entity has within a particular fictional universe or narrative setting.
-
D.
literaryRole
Indicates the specific narrative or functional role an entity holds within a literary work or text.
-
E.
producesRole
Indicates that one entity generates, creates, or gives rise to a particular role associated with another entity.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: May 1, 2026, 1:29 a.m.