Triple
T13363101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph Brocherel |
E318867
|
entity |
| Predicate | typeOfAchievement |
P9672
|
FINISHED |
| Object | pioneering ascent |
—
|
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: pioneering ascent | Statement: [Joseph Brocherel, typeOfAchievement, pioneering ascent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAchievement Context triple: [Joseph Brocherel, typeOfAchievement, pioneering ascent]
-
A.
achievementDefinition
Indicates that one entity specifies or defines the criteria, properties, or structure of an achievement associated with another entity.
-
B.
isIndividualAchievement
Indicates that the achievement is attributed to a single individual rather than to a group or collective effort.
-
C.
placeOfAchievement
Indicates the location where an entity accomplished or attained a particular achievement or notable success.
-
D.
achievementScope
Indicates the extent or domain within which an achievement is recognized, measured, or considered valid.
-
E.
associatedAchievement
chosen
Indicates a relationship where one entity is linked to, or recognized in connection with, a particular achievement.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da628affd081909f1790d333f0eef4 |
completed | April 11, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.