Triple
T19368899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klemens Murańka |
E484477
|
entity |
| Predicate | hasSetRecord |
P92054
|
FINISHED |
| Object | junior hill record |
—
|
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: junior hill record | Statement: [Klemens Murańka, hasSetRecord, junior hill record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSetRecord Context triple: [Klemens Murańka, hasSetRecord, junior hill record]
-
A.
setRecordFor
chosen
Indicates establishing or updating a specific record associated with an entity or context.
-
B.
hasWorkRecordedThere
Indicates that a person or creator has had their work documented, produced, or otherwise officially recorded at a particular place or institution.
-
C.
hasWrittenRecordsIn
Indicates that an entity has produced or maintains written records in a specified medium, format, or location.
-
D.
hasSetForm
Indicates that something possesses or is associated with a specific, defined form or configuration as part of a set.
-
E.
hasSeriesRecord
Indicates that one entity maintains a documented record or history of another entity’s participation or performance within a series.
- 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.