Triple
T25230324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himmela |
E632202
|
entity |
| Predicate | roleInPerformance |
P148906
|
FINISHED |
| Object | supports dancers and actors |
—
|
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: supports dancers and actors | Statement: [Himmela, roleInPerformance, supports dancers and actors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPerformance Context triple: [Himmela, roleInPerformance, supports dancers and actors]
-
A.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
-
B.
theaterRole
Indicates that an entity holds or performs a specific role or character in a theatrical production in relation to another entity (such as a play or performance).
-
C.
performingArtRole
chosen
Indicates a role or function that an entity fulfills within the context of a performing arts activity or production.
-
D.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
E.
talentShowRole
Indicates the specific function or position an entity holds within the context of a talent show (e.g., performer, judge, host).
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 21, 2026, 1:04 p.m.