Triple
T25285596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nördlinger Ries impact crater |
E633928
|
entity |
| Predicate | impactTargetRocks |
P60800
|
FINISHED |
| Object | crystalline basement rocks |
—
|
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: crystalline basement rocks | Statement: [Nördlinger Ries impact crater, impactTargetRocks, crystalline basement rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactTargetRocks Context triple: [Nördlinger Ries impact crater, impactTargetRocks, crystalline basement rocks]
-
A.
impactTargetRock
chosen
Indicates that one entity strikes or collides with a rock as its target.
-
B.
impactOrigin
Indicates that one entity is the source or cause from which the impact or effect on another entity originates.
-
C.
impactExperimentTarget
Indicates that an experiment directly affects, influences, or produces a measurable impact on a specified target.
-
D.
impactStatus
Indicates the current state or condition of how something has affected or influenced a target.
-
E.
impactBuilding
Indicates that one entity physically collides with or strikes a building, causing an impact event.
- 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_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 1:19 p.m.