Triple
T20682518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wunda crater |
E508329
|
entity |
| Predicate | celestialBodyTypeOfLocation |
P60174
|
FINISHED |
| Object | natural satellite |
—
|
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: natural satellite | Statement: [Wunda crater, celestialBodyTypeOfLocation, natural satellite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: celestialBodyTypeOfLocation Context triple: [Wunda crater, celestialBodyTypeOfLocation, natural satellite]
-
A.
cosmicLocationType
Indicates the specific kind of spatial or cosmic setting in which an entity or event is situated (e.g., galaxy, nebula, star system).
-
B.
orbitalBodyType
chosen
Indicates the classification of an orbital body in terms of its type (e.g., planet, moon, asteroid, comet) within an orbital system.
-
C.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
D.
centralBody
Indicates that one object serves as the primary gravitational or reference body around which another object orbits or is defined.
-
E.
inSolarSystemBody
Indicates that one entity is located within, on, or as part of a specified solar system body (such as a planet, moon, or asteroid).
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6bea9771881908a077d01f53f6d52 |
completed | April 21, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:45 a.m.