Triple
T37936231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Polish winter K2 expedition |
E946357
|
entity |
| Predicate | expeditionLeaderRole |
P24306
|
FINISHED |
| Object | expedition leader |
—
|
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: expedition leader | Statement: [2018 Polish winter K2 expedition, expeditionLeaderRole, expedition leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expeditionLeaderRole Context triple: [2018 Polish winter K2 expedition, expeditionLeaderRole, expedition leader]
-
A.
notableExpeditionLeader
Indicates that the subject is recognized for having led an expedition that is historically or culturally notable.
-
B.
roleInExpedition
chosen
Indicates the specific function, duty, or position an entity holds within the context of a particular expedition.
-
C.
captainDuringExpedition
Indicates that an entity served as the captain of another entity (such as a ship, team, or mission) for the duration of a specific expedition.
-
D.
expeditionMemberOf
Indicates that an entity participates as a member in a specific expedition.
-
E.
ownerDuringExpedition
Indicates that one entity is the owner of another entity specifically for the duration of a particular expedition or journey.
- 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.