Triple
T10851709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pingualuit Crater |
E256160
|
entity |
| Predicate | impactStructure |
P63493
|
FINISHED |
| Object | simple bowl-shaped crater |
—
|
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: simple bowl-shaped crater | Statement: [Pingualuit Crater, impactStructure, simple bowl-shaped crater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactStructure Context triple: [Pingualuit Crater, impactStructure, simple bowl-shaped crater]
-
A.
impactStructureType
chosen
Indicates the type or nature of the structure that is affected or influenced by a given impact or action.
-
B.
identifiedAsImpactStructure
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.
-
C.
impactTargetRock
Indicates that one entity strikes or collides with a rock as its target.
-
D.
impactEvent
Indicates that one entity physically strikes or collides with another, producing a resulting effect or change.
-
E.
hasCrater
Indicates that one entity possesses or features a crater on its surface.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75117b76c8190b0fb216b1428c3c7 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.