Triple
T19368901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klemens Murańka |
E484477
|
entity |
| Predicate | hasCompetitorNumber |
P135676
|
FINISHED |
| Object | FIS code (ski jumping) |
—
|
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: FIS code (ski jumping) | Statement: [Klemens Murańka, hasCompetitorNumber, FIS code (ski jumping)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitorNumber Context triple: [Klemens Murańka, hasCompetitorNumber, FIS code (ski jumping)]
-
A.
competitorCount
Indicates the number of competitors associated with a given entity or context.
-
B.
hasCompetitionElement
Indicates that one entity includes, involves, or is associated with a specific competitive component, aspect, or feature.
-
C.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
D.
tieneCompetencia
Indicates that one entity has or faces competition from another entity.
-
E.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:35 p.m.