Triple
T5412526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copernicus (lunar crater) |
E121044
|
entity |
| Predicate | centralPeakComposition |
P63293
|
FINISHED |
| Object | uplifted crustal material |
—
|
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: uplifted crustal material | Statement: [Copernicus (lunar crater), centralPeakComposition, uplifted crustal material]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralPeakComposition Context triple: [Copernicus (lunar crater), centralPeakComposition, uplifted crustal material]
-
A.
isCentralPeakOf
Indicates that one entity is the main, elevated peak located near the center of another, typically larger, geological or impact structure.
-
B.
centralMoundHeight
Indicates the height measurement of a central mound relative to a defined reference level.
-
C.
centralRockName
Indicates that an entity has a specific name assigned to its central rock or primary rock feature.
-
D.
mountainComposition
Indicates the material or substance that makes up or predominates in a given mountain.
-
E.
centralBinaryComponent
Indicates that an entity functions as one of the primary stellar components in a central binary system.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87bb3c0c81908711784bc865ff03 |
completed | March 20, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd865702ec8190831bde2c2a331f28 |
completed | March 20, 2026, 5:39 p.m. |
Created at: March 20, 2026, 2:05 p.m.