Triple
T37936229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Polish winter K2 expedition |
E946357
|
entity |
| Predicate | baseCampArrival |
P189638
|
FINISHED |
| Object | 2018-01-08 |
—
|
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: 2018-01-08 | Statement: [2018 Polish winter K2 expedition, baseCampArrival, 2018-01-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseCampArrival Context triple: [2018 Polish winter K2 expedition, baseCampArrival, 2018-01-08]
-
A.
baseCampFor
Indicates that one location serves as the primary staging or support site for activities conducted in another location.
-
B.
baseCampType
Indicates the specific category or type assigned to a base camp within a given context or system.
-
C.
aboveBaseCamp
Indicates that one entity is located at a higher vertical position or elevation than the base camp.
-
D.
campLocation
Indicates the place or area where a camp is set up or located.
-
E.
typicalBaseCampArea
Indicates that a location is the usual or standard area used as a base camp for an activity, expedition, or operation.
- 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_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. |
| PDg | Predicate description generation | batch_69fbc7b6c2c88190ad4f58980834053c |
completed | May 6, 2026, 10:59 p.m. |
Created at: May 3, 2026, 4:20 p.m.