Triple
T28246443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganden Monastery |
E712180
|
entity |
| Predicate | hasMonasticColleges |
P164061
|
FINISHED |
| Object | Jangtse College |
—
|
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: Jangtse College | Statement: [Ganden Monastery, hasMonasticColleges, Jangtse College]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonasticColleges Context triple: [Ganden Monastery, hasMonasticColleges, Jangtse College]
-
A.
monasticColleges
chosen
Indicates that there is a relationship involving monastic colleges, typically linking an entity to the monastic educational or residential institutions with which it is associated.
-
B.
hasMonasticCommunities
Indicates that an entity possesses, hosts, or is associated with one or more monastic communities.
-
C.
hasColleges
Indicates that an entity possesses, contains, or is associated with one or more colleges.
-
D.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
-
E.
isPrincipalSeminaryOf
Indicates that one institution serves as the main or primary seminary associated with another entity.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 27, 2026, 11:01 p.m.