Triple
T28851314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annapurna Conservation Area |
E728601
|
entity |
| Predicate | hasCommunities |
P68541
|
FINISHED |
| Object | Gurung communities |
—
|
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: Gurung communities | Statement: [Annapurna Conservation Area, hasCommunities, Gurung communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunities Context triple: [Annapurna Conservation Area, hasCommunities, Gurung communities]
-
A.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
B.
hasCommunityGroups
Indicates that an entity is associated with one or more organized community groups or organizations.
-
C.
hasLocalCommunities
chosen
Indicates that an entity is associated with or contains smaller, localized community groups within a specific area or region.
-
D.
hasRemoteCommunities
Indicates that an entity maintains or is associated with communities located in distant or geographically isolated areas.
-
E.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fff59a00a881909b35b799654b3c45 |
completed | May 10, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69fff4d0a2e081909c972189b33d0128 |
completed | May 10, 2026, 3 a.m. |
Created at: April 28, 2026, 6:44 a.m.