Triple
T25282758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurinji (mountain landscape in Sangam tradition) |
E633861
|
entity |
| Predicate | typicalTerrain |
P189727
|
FINISHED |
| Object | mountainous region |
—
|
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 region | Statement: [Kurinji (mountain landscape in Sangam tradition), typicalTerrain, mountainous region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTerrain Context triple: [Kurinji (mountain landscape in Sangam tradition), typicalTerrain, mountainous region]
-
A.
hasGeneralTerrain
chosen
Indicates that an entity is characterized by or associated with a particular overall type of terrain.
-
B.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
C.
skiTerrainType
Indicates the type of terrain or surface on which the skiing activity takes place.
-
D.
landerType
Indicates the specific kind or category of lander involved in the relationship or action.
-
E.
involvesTerrain
Indicates that the relationship or action takes place in, across, or is directly affected by a specified type of terrain or landform.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.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 21, 2026, 1:19 p.m.