Triple
T17252359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baade P |
E418786
|
entity |
| Predicate | hasNameConvention |
P55768
|
FINISHED |
| Object | designated by parent crater name plus letter |
—
|
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: designated by parent crater name plus letter | Statement: [Baade P, hasNameConvention, designated by parent crater name plus letter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameConvention Context triple: [Baade P, hasNameConvention, designated by parent crater name plus letter]
-
A.
namingConventionType
chosen
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
B.
hasNaming
Indicates that one entity assigns, bears, or is associated with a specific name or designation provided by another entity.
-
C.
hasRuleName
Indicates that an entity is associated with a specific rule identified by a particular name.
-
D.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
-
E.
hasNameSuffix
Indicates that an entity’s name includes a specific suffix or ending component.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e694f788190a1c86e95264ed2fe |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.