Triple
T26312692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monpa people |
E661868
|
entity |
| Predicate | hasMajorMonastery |
P189949
|
FINISHED |
| Object | Tawang Monastery |
—
|
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: Tawang Monastery | Statement: [Monpa people, hasMajorMonastery, Tawang Monastery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorMonastery Context triple: [Monpa people, hasMajorMonastery, Tawang Monastery]
-
A.
containsMonastery
Indicates that one entity includes or encompasses a monastery within its boundaries or composition.
-
B.
hasNearbyMonastery
Indicates that one entity is located close to or in the vicinity of a monastery.
-
C.
principalMonasteryOf
chosen
Indicates that one monastery serves as the main or most important monastery associated with another entity (such as an order, region, or institution).
-
D.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
-
E.
monasteryType
Indicates the specific kind or classification of a monastery in relation to its broader religious or organizational category.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 26, 2026, 10:23 p.m.