Triple
T11078574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble (lunar crater) |
E261928
|
entity |
| Predicate | hasRimFeature |
P29932
|
FINISHED |
| Object | overlain by smaller impacts |
—
|
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: overlain by smaller impacts | Statement: [Hubble (lunar crater), hasRimFeature, overlain by smaller impacts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRimFeature Context triple: [Hubble (lunar crater), hasRimFeature, overlain by smaller impacts]
-
A.
hasRim
chosen
Indicates that one entity possesses or is equipped with a rim as a defining part or feature.
-
B.
hasRoadAlongRim
Indicates that a road runs adjacent to and follows the contour of a rim or edge of a geographic feature.
-
C.
hasMountingFeature
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
D.
hasVehicleFeature
Indicates that a vehicle possesses, includes, or is equipped with a specific feature or characteristic.
-
E.
hasFrontFeature
Indicates that an entity possesses a specific characteristic, component, or attribute located on its front side.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799953d58819096b645a1377e70f2 |
completed | April 9, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.