Triple
T35051864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsiolkovskiy B |
E1011349
|
entity |
| Predicate | namedFeatureCategory |
P118490
|
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 B, namedFeatureCategory, lunar crater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedFeatureCategory Context triple: [Tsiolkovskiy B, namedFeatureCategory, lunar crater]
-
A.
namedFeature
Indicates that an entity has a specific feature or attribute that is explicitly given a name.
-
B.
namedForFeature
Indicates that one entity is named after, or derives its name from, a particular feature or characteristic of another entity.
-
C.
featureDesignation
chosen
Indicates the specific label or name assigned to a feature to distinguish it from other features.
-
D.
labelFeatures
Indicates assigning descriptive tags or identifiers to specific features or attributes of an entity.
-
E.
mapCategory
Indicates that one category is associated with or translated into another category, typically to align or relate different classification schemes.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:01 p.m.