Triple
T5752211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I'm Just Ken |
E126878
|
entity |
| Predicate | featuredInSceneType |
P61635
|
FINISHED |
| Object | musical number |
—
|
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: musical number | Statement: [I'm Just Ken, featuredInSceneType, musical number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredInSceneType Context triple: [I'm Just Ken, featuredInSceneType, musical number]
-
A.
performedInSceneType
Indicates that an action or event was carried out within a scene of a specified type or category.
-
B.
partOfScene
Indicates that one entity functions as a component or element within a larger scene or setting involving another entity.
-
C.
sceneFeature
chosen
Indicates a characteristic, element, or attribute that is present within or helps define a particular scene.
-
D.
appearsInScriptType
Indicates that an entity is featured or occurs within a script of a specified type or category.
-
E.
featuredIn
Indicates that one entity appears or is prominently included within another entity, such as a person, work, or item being showcased in a larger work, event, or context.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b52663c8190ab44258468d4296d |
completed | March 22, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c021ca61688190875bd6107161c284 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.