Triple
T11673340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Asian Buddhism |
E277431
|
entity |
| Predicate | hasMonasticInstitution |
P74629
|
FINISHED |
| Object | Buddhist monastery |
—
|
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: Buddhist monastery | Statement: [East Asian Buddhism, hasMonasticInstitution, Buddhist monastery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonasticInstitution Context triple: [East Asian Buddhism, hasMonasticInstitution, Buddhist monastery]
-
A.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
-
B.
hasMonasticCommunities
chosen
Indicates that an entity possesses, hosts, or is associated with one or more monastic communities.
-
C.
containsMonastery
Indicates that one entity includes or encompasses a monastery within its boundaries or composition.
-
D.
monasteryAffiliation
Indicates a relationship where an entity is formally associated with, belongs to, or is under the authority of a particular monastery.
-
E.
hasMonasteryDedicatedTo
Indicates that a place or institution possesses a monastery whose religious dedication is to a specific figure, deity, or sacred concept.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a443b6848190a1eb6825fbc49d08 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.