Triple
T19205186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koryaksky |
E480212
|
entity |
| Predicate | hasSlopeFeatures |
P77075
|
FINISHED |
| Object | radial gullies |
—
|
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: radial gullies | Statement: [Koryaksky, hasSlopeFeatures, radial gullies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSlopeFeatures Context triple: [Koryaksky, hasSlopeFeatures, radial gullies]
-
A.
hasSlopeFeature
chosen
Indicates that an entity possesses or is characterized by a particular slope-related property or feature.
-
B.
hasSlopeProtection
Indicates that a slope or embankment is equipped with protective measures or structures to prevent erosion, instability, or damage.
-
C.
hasSlopeRating
Indicates that something (typically a golf course or hole) is associated with a specific slope rating value that quantifies its relative difficulty for bogey golfers compared to scratch golfers.
-
D.
hasIncline
Indicates that one entity possesses or exhibits a slope, tilt, or upward/downward angle relative to another reference.
-
E.
isOnSlopeOf
Indicates that one entity is located on the inclined surface or side of another entity, typically a sloping terrain or structure.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f99cc39c81909499b8d0b78b4665 |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:17 p.m.