Triple
T35187553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calvin |
E1016029
|
entity |
| Predicate | hasFavoriteActivity |
P195607
|
FINISHED |
| Object | playing with Hobbes |
—
|
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: playing with Hobbes | Statement: [Calvin, hasFavoriteActivity, playing with Hobbes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFavoriteActivity Context triple: [Calvin, hasFavoriteActivity, playing with Hobbes]
-
A.
hasPopularActivity
Indicates that an entity is associated with an activity that is widely favored, frequently engaged in, or well-liked by many people.
-
B.
hasLiveFavouriteStatus
Indicates that an entity currently holds a preferred or favorited status in a live or active context.
-
C.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
D.
hasRecommendedActivity
Indicates that one entity suggests or endorses a particular activity for another entity to perform or engage in.
-
E.
hasFanActivity
Indicates that an entity is associated with actions, behaviors, or engagement carried out by fans in relation to it.
- F. None of above. chosen
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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69fddac42c4081908568649058e86458 |
completed | May 8, 2026, 12:44 p.m. |
Created at: May 3, 2026, 4:02 p.m.