Triple
T30577291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hügelland |
E778284
|
entity |
| Predicate | hasTerrainForm |
P189727
|
FINISHED |
| Object | gently rolling hills |
—
|
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: gently rolling hills | Statement: [Hügelland, hasTerrainForm, gently rolling hills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerrainForm Context triple: [Hügelland, hasTerrainForm, gently rolling hills]
-
A.
hasTerrainFor
Indicates that a location or area possesses terrain suitable or designated for a particular use, activity, or feature.
-
B.
hasTerrainCharacter
Indicates that one entity possesses or exhibits a particular terrain-related feature or characteristic in relation to another entity.
-
C.
hasPrimaryTerrain
Indicates that an entity’s main or dominant type of terrain or land surface is a specified terrain category.
-
D.
hasGeneralTerrain
chosen
Indicates that an entity is characterized by or associated with a particular overall type of terrain.
-
E.
hasAdvancedTerrain
Indicates that an entity possesses or is associated with terrain featuring complex, challenging, or enhanced physical characteristics beyond standard ground conditions.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 29, 2026, 8:23 p.m.