Triple
T28161248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kallar Syedan Tehsil |
E714899
|
entity |
| Predicate | hasDominantTerrain |
P154951
|
FINISHED |
| Object | Undulating plains |
—
|
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: Undulating plains | Statement: [Kallar Syedan Tehsil, hasDominantTerrain, Undulating plains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDominantTerrain Context triple: [Kallar Syedan Tehsil, hasDominantTerrain, Undulating plains]
-
A.
hasPrimaryTerrain
chosen
Indicates that an entity’s main or dominant type of terrain or land surface is a specified terrain category.
-
B.
hasMountainousTerrain
Indicates that a location or area possesses predominantly mountainous physical terrain or landscape features.
-
C.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
D.
dominantLandformOf
Indicates that one landform is the primary or most characteristic physical feature of a specified geographic area.
-
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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 10:06 p.m.