Triple
T11500220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achanakmar-Amarkantak Biosphere Reserve |
E272642
|
entity |
| Predicate | humanActivities |
P8834
|
FINISHED |
| Object | regulated tourism |
—
|
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: regulated tourism | Statement: [Achanakmar-Amarkantak Biosphere Reserve, humanActivities, regulated tourism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanActivities Context triple: [Achanakmar-Amarkantak Biosphere Reserve, humanActivities, regulated tourism]
-
A.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
B.
activityType
chosen
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
C.
otherActivity
Indicates that an entity is engaged in an activity that is different from a primary, specified, or expected activity.
-
D.
activity
Indicates that an entity is engaged in or performing a particular action, behavior, or process.
-
E.
pastoralActivities
Indicates activities related to providing spiritual care, guidance, or religious leadership within a community.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de3e9c881909d6c55334f7a832d |
completed | April 10, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.