Triple
T14160864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IAU lunar nomenclature |
E350940
|
entity |
| Predicate | coversFeatureType |
P101663
|
FINISHED |
| Object | lunar craters |
—
|
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 craters | Statement: [IAU lunar nomenclature, coversFeatureType, lunar craters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversFeatureType Context triple: [IAU lunar nomenclature, coversFeatureType, lunar craters]
-
A.
includesFeatureTypes
chosen
Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
-
B.
hasCoverFeature
Indicates that one entity serves as a prominent or featured element on the cover of another entity (such as a publication, product, or media item).
-
C.
coversTypeOfSite
Indicates that one entity provides coverage or applies to a particular category or type of site.
-
D.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
E.
coversActionType
Indicates that one entity’s scope, responsibility, or applicability includes or encompasses a particular type of action.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61393f308190bb357e2bd1916f94 |
completed | April 14, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:59 a.m.