Triple
T27927371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sera Monastery |
E707874
|
entity |
| Predicate | debatePracticeFrequency |
P163982
|
FINISHED |
| Object | daily (in the afternoon, traditionally) |
—
|
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: daily (in the afternoon, traditionally) | Statement: [Sera Monastery, debatePracticeFrequency, daily (in the afternoon, traditionally)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: debatePracticeFrequency Context triple: [Sera Monastery, debatePracticeFrequency, daily (in the afternoon, traditionally)]
-
A.
canDebate
Indicates that one entity has the ability or permission to engage in a debate or argumentative discussion with another entity.
-
B.
dealFrequency
Indicates how often a particular deal, transaction, or agreement occurs within a given period.
-
C.
canSpeakInDebates
Indicates that an entity has the ability or permission to speak during formal debates.
-
D.
areDebatesOf
Indicates that the subject entities are debates that concern, involve, or are associated with the object entities.
-
E.
hasDebateAround
Indicates that there is ongoing discussion, disagreement, or controversy surrounding the referenced entity or topic.
- F. None of above. chosen
Provenance (4 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_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 7:01 p.m.