Triple
T35828564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsiolkovskiy Q |
E1035724
|
entity |
| Predicate | hasCelestialBodyType |
P62445
|
FINISHED |
| Object | lunar crater |
—
|
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: lunar crater | Statement: [Tsiolkovskiy Q, hasCelestialBodyType, lunar crater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCelestialBodyType Context triple: [Tsiolkovskiy Q, hasCelestialBodyType, lunar crater]
-
A.
orbitalBodyType
Indicates the classification of an orbital body in terms of its type (e.g., planet, moon, asteroid, comet) within an orbital system.
-
B.
containsPlanetType
Indicates that one entity includes or encompasses a planet of a specified type within its scope or composition.
-
C.
hasPlanetaryFeatureType
chosen
Indicates that an entity possesses or is associated with a specific type of planetary surface or geological feature.
-
D.
hasCentralPlanetType
Indicates that an entity has a central planet whose type or classification is specified by the related value.
-
E.
hasGalacticObjectType
Indicates that an entity is associated with, or classified as, a specific type of galactic object.
- 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:06 p.m.