Triple
T25285581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nördlinger Ries impact crater |
E633928
|
entity |
| Predicate | identifiedAsImpactStructureIn |
P38855
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Nördlinger Ries impact crater, identifiedAsImpactStructureIn, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiedAsImpactStructureIn Context triple: [Nördlinger Ries impact crater, identifiedAsImpactStructureIn, 1960s]
-
A.
identifiedAsImpactStructure
chosen
Indicates that something has been determined or classified as an impact structure, typically formed by the collision of an extraterrestrial body with a planetary surface.
-
B.
impactStructureType
Indicates the type or nature of the structure that is affected or influenced by a given impact or action.
-
C.
isNamedCraterOn
Indicates that a crater bears a specific name and is located on a particular celestial body.
-
D.
partOfCraterSystem
Indicates that one crater is a component or subdivision of a larger, connected crater system.
-
E.
locatedInCrater
Indicates that one entity is situated within the boundaries of a specific crater.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e0921ac8190a4a8fec7be7ad8f6 |
completed | May 1, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:19 p.m.