Triple
T11976253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bride Peak |
E285047
|
entity |
| Predicate | notableAttemptYear |
P87721
|
FINISHED |
| Object | 1957 |
—
|
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: 1957 | Statement: [Bride Peak, notableAttemptYear, 1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAttemptYear Context triple: [Bride Peak, notableAttemptYear, 1957]
-
A.
notableAttempt
Indicates that an entity made a significant or noteworthy effort to perform or achieve another entity or outcome.
-
B.
notableWorkYear
Indicates the year in which a notable work associated with an entity was created, released, or achieved prominence.
-
C.
notablePerformanceYear
Indicates the year in which an entity delivered a particularly significant or distinguished performance.
-
D.
notableStatistic
Indicates that a particular statistic is especially significant or noteworthy in relation to the subject.
-
E.
hasNotableYear
chosen
Indicates that an entity is associated with a specific year that is particularly significant or noteworthy for it.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.