Triple
T25285594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nördlinger Ries impact crater |
E633928
|
entity |
| Predicate | impactAngle |
P107108
|
FINISHED |
| Object | oblique impact |
—
|
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: oblique impact | Statement: [Nördlinger Ries impact crater, impactAngle, oblique impact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactAngle Context triple: [Nördlinger Ries impact crater, impactAngle, oblique impact]
-
A.
dropAngle
Indicates the angle at which something is dropped or released relative to a reference direction or surface.
-
B.
angleOfIncident
chosen
Indicates the angle at which one entity (such as a ray, line, or object) strikes or approaches the surface or boundary of another entity.
-
C.
impactStatus
Indicates the current state or condition of how something has affected or influenced a target.
-
D.
impactOrigin
Indicates that one entity is the source or cause from which the impact or effect on another entity originates.
-
E.
inclinationAngle
Indicates the angle at which one object or reference frame is tilted or inclined relative to another specified baseline or plane.
- 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_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 1:19 p.m.