Triple
T30054845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paro District |
E763696
|
entity |
| Predicate | hasFortressMonastery |
P20652
|
FINISHED |
| Object | Rinpung Dzong |
—
|
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: Rinpung Dzong | Statement: [Paro District, hasFortressMonastery, Rinpung Dzong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFortressMonastery Context triple: [Paro District, hasFortressMonastery, Rinpung Dzong]
-
A.
containsMonastery
chosen
Indicates that one entity includes or encompasses a monastery within its boundaries or composition.
-
B.
monasteryBuiltInto
Indicates that a monastery is physically constructed within, attached to, or integrated into a natural or man-made structure such as a cliff, cave, or building.
-
C.
hasMonasteryRuins
Indicates that an entity possesses or contains the remains or ruins of a former monastery.
-
D.
monasteryType
Indicates the specific kind or classification of a monastery in relation to its broader religious or organizational category.
-
E.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 29, 2026, 6:56 p.m.