Triple
T30778250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Bourdillon |
E783736
|
entity |
| Predicate | expeditionLeaderOnEverest1953 |
P170123
|
FINISHED |
| Object | John Hunt |
—
|
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: John Hunt | Statement: [Tom Bourdillon, expeditionLeaderOnEverest1953, John Hunt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expeditionLeaderOnEverest1953 Context triple: [Tom Bourdillon, expeditionLeaderOnEverest1953, John Hunt]
-
A.
notableExpeditionLeader
Indicates that the subject is recognized for having led an expedition that is historically or culturally notable.
-
B.
firstMajorClimbingExpeditionYear
Indicates the year in which the first significant or major climbing expedition to a particular location took place.
-
C.
firstRecordedAsClimbedBy
Indicates the person or group who is credited with making the first recorded ascent of a particular climb or peak.
-
D.
attemptedFirstAscentOf
Indicates that an entity made an effort to be the first to successfully climb or reach the summit of a particular route, peak, or feature.
-
E.
numberOfMenOnExpedition
Indicates the count of male individuals participating in a given expedition.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fe2a3ec8190a75f3d2f21ff14f7 |
completed | May 2, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f68848ad348190a2fb6e841dcfdb7d |
completed | May 2, 2026, 11:27 p.m. |
Created at: April 29, 2026, 8:41 p.m.