Triple
T13859401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narripaidat |
E333147
|
entity |
| Predicate | isPopularBecause |
P55574
|
FINISHED |
| Object | distinctive jester-themed design of Jokerit jerseys |
—
|
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: distinctive jester-themed design of Jokerit jerseys | Statement: [Narripaidat, isPopularBecause, distinctive jester-themed design of Jokerit jerseys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularBecause Context triple: [Narripaidat, isPopularBecause, distinctive jester-themed design of Jokerit jerseys]
-
A.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
-
B.
isPopularWith
Indicates that one entity is well-liked, favored, or widely accepted by another entity or group.
-
C.
isPopularAt
Indicates that an entity enjoys a high level of recognition, approval, or favor within a specified place, context, or time.
-
D.
isPopularOnSocialMedia
Indicates that an entity is widely followed, frequently engaged with, or broadly recognized across social media platforms.
-
E.
hasPopularityReason
chosen
Indicates that there is a specific reason or factor explaining why something is popular.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02de38e48190b6ead95561031c32 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.