Triple
T30778267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Bourdillon |
E783736
|
entity |
| Predicate | climbedRegion |
P40022
|
FINISHED |
| Object | Alps |
—
|
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: Alps | Statement: [Tom Bourdillon, climbedRegion, Alps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbedRegion Context triple: [Tom Bourdillon, climbedRegion, Alps]
-
A.
alsoClimbed
Indicates that one entity climbed something that another specified entity also climbed.
-
B.
highestPeakClimbed
Indicates the tallest mountain or peak that an entity has successfully climbed.
-
C.
mountainRangeClimbedIn
chosen
Indicates that a particular mountain range is the location in which a climbing activity or ascent took place.
-
D.
climbedFeatureType
Indicates that an entity has climbed or ascended a particular type of physical feature (such as a mountain, wall, or similar structure).
-
E.
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.
- 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_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_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:41 p.m.