Triple
T29832018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kel Ahaggar |
E757548
|
entity |
| Predicate | terrainOfTerritory |
P159101
|
FINISHED |
| Object | mountainous desert |
—
|
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: mountainous desert | Statement: [Kel Ahaggar, terrainOfTerritory, mountainous desert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrainOfTerritory Context triple: [Kel Ahaggar, terrainOfTerritory, mountainous desert]
-
A.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
B.
territoryFeature
chosen
Indicates that a specific geographic or physical feature is located within, characterizes, or is part of a given territory.
-
C.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
D.
terrainIncludes
Indicates that a specified terrain area contains or encompasses another geographic or environmental feature within its boundaries.
-
E.
landerType
Indicates the specific kind or category of lander involved in the relationship or action.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6759cbec481908ef7619ff4c755d9 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:34 p.m.