Triple
T31498897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tipra |
E803620
|
entity |
| Predicate | majorityInHillAreasOf |
P197451
|
FINISHED |
| Object | Tripura |
—
|
NE NERFINISHED |
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: Tripura | Statement: [Tipra, majorityInHillAreasOf, Tripura]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorityInHillAreasOf Context triple: [Tipra, majorityInHillAreasOf, Tripura]
-
A.
locatedInHills
Indicates that something is situated within or among hilly terrain or a region characterized by hills.
-
B.
isInValleyOrMountainRegion
Indicates that an entity is located within either a valley area or a mountainous region.
-
C.
hasMountainousTerrain
Indicates that a location or area possesses predominantly mountainous physical terrain or landscape features.
-
D.
hasMajorMountainRange
Indicates that one entity possesses, contains, or is geographically associated with a principal or significant mountain range.
-
E.
containsHill
Indicates that one entity geographically includes or encompasses a hill within its area or boundaries.
- F. None of above. chosen
Provenance (4 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
| PDg | Predicate description generation | batch_69fe9208ed708190980fb5061b22ae49 |
completed | May 9, 2026, 1:46 a.m. |
Created at: April 30, 2026, 9:43 p.m.