Triple
T19368898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klemens Murańka |
E484477
|
entity |
| Predicate | hasJuniorCareer |
P109052
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Klemens Murańka, hasJuniorCareer, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJuniorCareer Context triple: [Klemens Murańka, hasJuniorCareer, yes]
-
A.
hasJuniorStatus
Indicates that one entity holds a lower, subordinate, or less senior status relative to another entity within a defined hierarchy or context.
-
B.
hasJuniorAgeCategory
chosen
Indicates that an entity is associated with, or classified under, a junior age category within a given context or system.
-
C.
hasStageCareer
Indicates that an entity has pursued or been involved in a professional career in stage performance or theater.
-
D.
hasJuniorSection
Indicates that an entity includes or is associated with a subordinate or lower-level section within its structure or organization.
-
E.
hasJuniorDraftEligibility
Indicates that an individual meets the criteria to be eligible for selection in a junior-level draft.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619ae6838819080584d60cbd58bbd |
completed | April 20, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.