Triple
T33552347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1996 Mount Everest disaster |
E859371
|
entity |
| Predicate | involvedExpedition |
P194320
|
FINISHED |
| Object | Adventure Consultants expedition |
—
|
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: Adventure Consultants expedition | Statement: [1996 Mount Everest disaster, involvedExpedition, Adventure Consultants expedition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedExpedition Context triple: [1996 Mount Everest disaster, involvedExpedition, Adventure Consultants expedition]
-
A.
relatedExpedition
Indicates that one expedition has a connection or association with another expedition, such as being part of the same project, time period, or thematic context.
-
B.
issExpedition
Indicates an expedition or mission associated with the International Space Station (ISS).
-
C.
expeditionMemberOf
Indicates that an entity participates as a member in a specific expedition.
-
D.
describesExpedition
Indicates that one entity provides a detailed account or characterization of an expedition undertaken by another entity.
-
E.
usedByExpedition
Indicates that something (such as an object, resource, or method) is utilized or employed by an expedition in the course of its activities.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
| PDg | Predicate description generation | batch_69fd6a1a38f081908c573aee4696de4f |
completed | May 8, 2026, 4:44 a.m. |
Created at: May 1, 2026, 1:39 a.m.