Triple
T37936252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Polish winter K2 expedition |
E946357
|
entity |
| Predicate | rescueParticipant |
P858
|
FINISHED |
| Object | Adam Bielecki |
—
|
NE NERFINISHED |
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: Adam Bielecki | Statement: [2018 Polish winter K2 expedition, rescueParticipant, Adam Bielecki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescueParticipant Context triple: [2018 Polish winter K2 expedition, rescueParticipant, Adam Bielecki]
-
A.
participantFrom
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
-
B.
partnerInRescue
Indicates a relationship where two or more entities collaborate as partners in carrying out a rescue effort or operation.
-
C.
participantWith
Indicates that an entity takes part in an event, activity, or process together with another specified entity.
-
D.
allegedParticipant
Indicates that an entity is claimed or suspected to have taken part in an event, action, or situation, without this participation being confirmed as fact.
-
E.
participant
chosen
Indicates that an entity takes part in, is involved in, or plays a role within a specified event, activity, or process.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.