Triple
T2096621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crater Lake National Park |
E36995
|
entity |
| Predicate | formationPeriod |
P25023
|
FINISHED |
| Object | about 7,700 years ago |
—
|
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: about 7,700 years ago | Statement: [Crater Lake National Park, formationPeriod, about 7,700 years ago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formationPeriod Context triple: [Crater Lake National Park, formationPeriod, about 7,700 years ago]
-
A.
foundingPeriod
Indicates the time span or historical period during which an entity (such as an organization, settlement, or institution) was founded.
-
B.
formedAt
chosen
Indicates the time or date at which an entity was created, established, or came into existence.
-
C.
reorganizationPeriod
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
-
D.
formerNamePeriodStart
Indicates the date or time point when an entity began using a former name that is being recorded.
-
E.
establishedTransitionPeriod
Indicates that an entity has formally set or defined a specific transition period between two states, conditions, or arrangements.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba9b1f048190b82adfb7d8814173 |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.