Triple
T32513758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krusty the Clown Show |
E831003
|
entity |
| Predicate | notableInUniverseFan |
P68978
|
FINISHED |
| Object | Bart Simpson |
E199538
|
NE 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: Bart Simpson | Statement: [Krusty the Clown Show, notableInUniverseFan, Bart Simpson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInUniverseFan Context triple: [Krusty the Clown Show, notableInUniverseFan, Bart Simpson]
-
A.
notedForInUniverse
Indicates that an entity is recognized or distinguished for a particular trait, role, or achievement within a specific fictional universe or narrative continuity.
-
B.
notableFandom
Indicates that an entity is significantly recognized for having a dedicated or prominent fan base centered around it.
-
C.
notableFan
chosen
Indicates that one entity is a well-known or especially prominent admirer or supporter of another entity.
-
D.
notableCanon
Indicates that the subject is a significant or widely recognized part of the established canon associated with the object.
-
E.
basisInUniverse
Indicates that one entity serves as the foundational basis or underlying grounding for another entity within a given universe or domain.
- F. None of above.
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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35813113908190ad02a2b9a6e4b39e |
completed | June 19, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1 a.m.