Triple
T24353126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Field |
E613847
|
entity |
| Predicate | DarbyFieldNotability |
P155898
|
FINISHED |
| Object | first recorded European to climb Mount Washington |
—
|
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: first recorded European to climb Mount Washington | Statement: [Mount Field, DarbyFieldNotability, first recorded European to climb Mount Washington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DarbyFieldNotability Context triple: [Mount Field, DarbyFieldNotability, first recorded European to climb Mount Washington]
-
A.
designerNotability
Indicates that an entity is notable or recognized specifically for its work or role as a designer.
-
B.
notabilityScope
Indicates the domain, field, or context within which something is considered notable or significant.
-
C.
organNotability
Indicates that an organ is notable or significant in some specific context or for a particular purpose.
-
D.
notabilityStatus
Indicates whether and how an entity is recognized as notable or significant within a given context or system.
-
E.
coachNotability
Indicates that an individual is notable or distinguished specifically in their role as a coach.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2934732908190a50e69f492a5dc7a |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 1:59 a.m.