Triple
T21031454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reinhold (lunar crater) |
E518071
|
entity |
| Predicate | featureTypeCode |
P5048
|
FINISHED |
| Object | CR |
—
|
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: CR | Statement: [Reinhold (lunar crater), featureTypeCode, CR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureTypeCode Context triple: [Reinhold (lunar crater), featureTypeCode, CR]
-
A.
featureType
chosen
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
B.
featureTypeCatalog
Indicates that an entity is associated with, or defined by, a catalog that specifies the types of features it can include or reference.
-
C.
featureDesignation
Indicates the specific label or name assigned to a feature to distinguish it from other features.
-
D.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
E.
targetFeature
Indicates that one entity is the specific feature, attribute, or characteristic that another entity is directed toward, focused on, or intended to affect.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc82b5348190b449d59e6cada9de |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.