Triple
T18942812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Hockey League mascots |
E463428
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | entertainment character group |
C21020
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: entertainment character group Context triple: [National Hockey League mascots, instanceOf, entertainment character group]
-
A.
character group
chosen
A character group is a collection of characters that share common traits, roles, or relationships within a narrative or setting, functioning together as a cohesive unit.
-
B.
animated television characters group
A group of animated television characters represents a collection of fictional, stylized personas designed for TV shows, often interacting within shared storylines, settings, or themes.
-
C.
character database
A character database is a structured repository that stores, organizes, and manages detailed information about fictional or real-world characters, including their attributes, relationships, histories, and appearances for easy retrieval and analysis.
-
D.
character group in the Mahabharata
A character group in the Mahabharata is a set of individuals—such as families, factions, or allied kingdoms—linked by kinship, loyalty, or shared purpose, whose collective actions and relationships drive the epic’s narrative and moral conflicts.
-
E.
theatrical character
A theatrical character is a fictional persona created for and portrayed within a stage performance, embodying specific traits, motivations, and relationships that drive the drama.
- F. None of above.
Provenance (1 batch)
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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:59 a.m.