Triple
T25105323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lehua |
E628850
|
entity |
| Predicate | hasSteepInteriorCraterWalls |
P165298
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lehua, hasSteepInteriorCraterWalls, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSteepInteriorCraterWalls Context triple: [Lehua, hasSteepInteriorCraterWalls, true]
-
A.
hasMultipleCraters
Indicates that an entity possesses or is characterized by more than one crater.
-
B.
hasSatelliteCrater
Indicates that one crater is a secondary or subsidiary crater associated with, and typically located near, another primary crater.
-
C.
hasHeavilyCrateredSurface
Indicates that the subject’s surface is densely covered with impact craters, showing extensive cratering relative to typical surfaces.
-
D.
hasCrater
Indicates that one entity possesses or features a crater on its surface.
-
E.
mainCrater
Indicates that one crater is the primary or most significant crater associated with another crater or crater-related feature.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 18, 2026, 6:26 a.m.