Triple
T28127474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drepung Monastery |
E710967
|
entity |
| Predicate | nearbyMonasteries |
P43982
|
FINISHED |
| Object | Sera 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: Sera Monastery | Statement: [Drepung Monastery, nearbyMonasteries, Sera Monastery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyMonasteries Context triple: [Drepung Monastery, nearbyMonasteries, Sera Monastery]
-
A.
monasteryNearbyPeriod
Indicates that a monastery is located near a place or entity during a specified time period.
-
B.
monasteryNearbyArchitectureStyle
Indicates that a monastery is located close to a structure or area characterized by a particular architectural style.
-
C.
hasNearbyMonastery
chosen
Indicates that one entity is located close to or in the vicinity of a monastery.
-
D.
nearReligiousSite
Indicates that one entity is located close to or in the immediate vicinity of a religious site.
-
E.
monasticCenters
Indicates that one entity serves as a monastic center or hub for religious monastic life in relation to 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 27, 2026, 9:21 p.m.