Triple
T27927370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sera Monastery |
E707874
|
entity |
| Predicate | debatePracticeLocation |
P158619
|
FINISHED |
| Object | monastic debate courtyard |
—
|
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: monastic debate courtyard | Statement: [Sera Monastery, debatePracticeLocation, monastic debate courtyard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: debatePracticeLocation Context triple: [Sera Monastery, debatePracticeLocation, monastic debate courtyard]
-
A.
debateLocation
chosen
Indicates the place or venue where a debate occurs or is held.
-
B.
debateOrganizer
Indicates that one entity is responsible for organizing, coordinating, or managing a debate involving another entity or entities.
-
C.
settingOfDebate
Indicates the context, environment, or circumstances in which a particular debate takes place.
-
D.
positionOnDebate
Indicates the stance or viewpoint an entity holds regarding a particular debate or controversial issue.
-
E.
canDebate
Indicates that one entity has the ability or permission to engage in a debate or argumentative discussion 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:01 p.m.