Triple
T25663444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yosemite climbing community |
E643446
|
entity |
| Predicate | hadNotableEra |
P561
|
FINISHED |
| Object | Stone Masters era |
—
|
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: Stone Masters era | Statement: [Yosemite climbing community, hadNotableEra, Stone Masters era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNotableEra Context triple: [Yosemite climbing community, hadNotableEra, Stone Masters era]
-
A.
notableEra
chosen
Indicates the historical period or era for which an entity is especially recognized or significant.
-
B.
bearerNotableEra
Indicates that a bearer (such as a title, role, or office) is notably associated with a particular historical era or time period.
-
C.
associatedWithNotableEra
Indicates that something has a significant connection or relevance to a historically or culturally notable period of time.
-
D.
notableEraStart
Indicates the point in time when a notable or historically significant era associated with an entity begins.
-
E.
hasNotableYear
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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 6:58 p.m.