Triple
T16779485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michal |
E407818
|
entity |
| Predicate | keyThemeConnection |
P20616
|
FINISHED |
| Object | storytelling and responsibility |
—
|
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: storytelling and responsibility | Statement: [Michal, keyThemeConnection, storytelling and responsibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyThemeConnection Context triple: [Michal, keyThemeConnection, storytelling and responsibility]
-
A.
keyThemeIn
Indicates that a particular theme is a central or primary thematic focus within a given work, context, or subject.
-
B.
centralThemeConnection
Indicates a relationship where one element serves as the primary or unifying theme that conceptually links or organizes the other element(s).
-
C.
hasThemeConnection
chosen
Indicates a relationship where one entity is linked to another through a shared or related theme, topic, or conceptual focus.
-
D.
themeKey
Indicates that one entity serves as the primary subject, topic, or thematic focus associated with another entity.
-
E.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21401b881909bbbc7382e851a90 |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.