Triple
T26847101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Tibet |
E675954
|
entity |
| Predicate | hasMonasticNetwork |
P74629
|
FINISHED |
| Object | major Gelug monasteries |
—
|
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: major Gelug monasteries | Statement: [Central Tibet, hasMonasticNetwork, major Gelug monasteries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonasticNetwork Context triple: [Central Tibet, hasMonasticNetwork, major Gelug monasteries]
-
A.
hasParishNetwork
Indicates that an entity is connected to or served by a specific parish or group of parishes within an ecclesiastical or community network.
-
B.
hasMonasticCommunities
chosen
Indicates that an entity possesses, hosts, or is associated with one or more monastic communities.
-
C.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
-
D.
hasMonasticName
Indicates that an entity possesses a specific name adopted or assigned within a monastic or religious order.
-
E.
hasTempleNetwork
Indicates that an entity maintains or is part of an interconnected system or network of temples.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 5:13 a.m.