Triple
T14012682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nekodake |
E337122
|
entity |
| Predicate | hasDistinctiveTopography |
P22129
|
FINISHED |
| Object | jagged summit ridge |
—
|
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: jagged summit ridge | Statement: [Nekodake, hasDistinctiveTopography, jagged summit ridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctiveTopography Context triple: [Nekodake, hasDistinctiveTopography, jagged summit ridge]
-
A.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
B.
hasMountainousTerrain
Indicates that a location or area possesses predominantly mountainous physical terrain or landscape features.
-
C.
topographicalCategory
Indicates the type of landform or surface feature that characterizes the physical terrain associated with an entity.
-
D.
hasLandscapeFeatures
chosen
Indicates that an entity possesses or includes specific landscape-related characteristics or elements.
-
E.
topographyBasedOn
Indicates that the topographical characteristics of one entity are derived from, determined by, or modeled using the topography of another entity.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f37d11481909159bdb9e1e8d38e |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.