Triple
T30081837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amaravati Buddhist Monastery |
E764486
|
entity |
| Predicate | hasRetreatFormat |
P139556
|
FINISHED |
| Object | silent retreats |
—
|
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: silent retreats | Statement: [Amaravati Buddhist Monastery, hasRetreatFormat, silent retreats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRetreatFormat Context triple: [Amaravati Buddhist Monastery, hasRetreatFormat, silent retreats]
-
A.
hasRetreatType
chosen
Indicates the specific category or type of retreat associated with an entity.
-
B.
hasRetreatPattern
Indicates that an entity follows a specific, identifiable pattern or strategy when withdrawing, backing off, or retreating from a situation or interaction.
-
C.
hasRetreatExposing
Indicates that an entity has a retreat or fallback position that, when used, exposes it or makes it vulnerable in some way.
-
D.
hasRetreated
Indicates that an entity has withdrawn or moved back from a previous position, engagement, or situation.
-
E.
hasRetreatedSince
Indicates that an entity has withdrawn or moved back from a position or engagement at some point after a specified reference time or event.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00512437d48190ad20324968ead5f4 |
completed | May 10, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a0050227350819099f41369c3d168be |
completed | May 10, 2026, 9:30 a.m. |
Created at: April 29, 2026, 7:03 p.m.