Triple
T13644983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muppet Studios |
E326078
|
entity |
| Predicate | hasTypeOfExperience |
P22183
|
FINISHED |
| Object | themed entertainment |
—
|
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: themed entertainment | Statement: [Muppet Studios, hasTypeOfExperience, themed entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfExperience Context triple: [Muppet Studios, hasTypeOfExperience, themed entertainment]
-
A.
typeOfExperience
chosen
Indicates that one entity specifies the category or nature of an experience associated with another entity.
-
B.
experienceType
Indicates the specific kind or category of experience associated with an entity or event.
-
C.
hasGlobalExperience
Indicates that an entity possesses experience gained from working, operating, or engaging across multiple countries or international contexts.
-
D.
recommendedExperience
Indicates that a certain level or type of prior experience is advised or preferred for engaging in the related activity, role, or item.
-
E.
experienceIncludes
Indicates that a particular experience encompasses, contains, or involves a specified component, activity, or element as part of it.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.