Triple
T25750546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GRAIL |
E648458
|
entity |
| Predicate | impactFeatureName |
P163850
|
FINISHED |
| Object | Sally Ride Crater |
—
|
NE NERFINISHED |
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: Sally Ride Crater | Statement: [GRAIL, impactFeatureName, Sally Ride Crater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactFeatureName Context triple: [GRAIL, impactFeatureName, Sally Ride Crater]
-
A.
featuresInfluence
Indicates that certain features or characteristics have an effect on or contribute to changes in other features, outcomes, or behaviors.
-
B.
impactDescription
Indicates a description of the effect, consequence, or influence that one entity, action, or event has on another.
-
C.
impactCategory
Indicates the type or domain of effect that one entity or action has on another, classifying the nature of its impact.
-
D.
impactStatus
Indicates the current state or condition of how something has affected or influenced a target.
-
E.
impactOrigin
Indicates that one entity is the source or cause from which the impact or effect on another entity originates.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 22, 2026, 4:34 a.m.