Triple
T27149054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valhalla impact structure |
E682331
|
entity |
| Predicate | ringSpacing |
P161908
|
FINISHED |
| Object | rings become more widely spaced with distance from center |
—
|
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: rings become more widely spaced with distance from center | Statement: [Valhalla impact structure, ringSpacing, rings become more widely spaced with distance from center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ringSpacing Context triple: [Valhalla impact structure, ringSpacing, rings become more widely spaced with distance from center]
-
A.
boreSpacing
Indicates the center-to-center distance between adjacent bores or holes in a component or assembly.
-
B.
ringRadius
Indicates the size of a ring by specifying the distance from its center to its outer edge.
-
C.
ringType
Indicates the specific kind or category of ring associated with an entity or relationship.
-
D.
hasRingGap
Indicates that there is a discontinuity or missing segment in a ring-like structure or arrangement between the related entities.
-
E.
webbingSpacing
Indicates the distance or interval between adjacent segments or strands of webbing in a structure or material.
- F. None of above. chosen
Provenance (4 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f624c8b4148190990ea6bd13e9e271 |
completed | May 2, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 9:13 a.m.