Triple
T5969009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varlaam Monastery |
E132824
|
entity |
| Predicate | monasticCommunityEstablished |
P52045
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Varlaam Monastery, monasticCommunityEstablished, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasticCommunityEstablished Context triple: [Varlaam Monastery, monasticCommunityEstablished, 16th century]
-
A.
monasteryEstablished
chosen
Indicates that a monastery was founded or formally established at a particular time, place, or by a specific agent.
-
B.
placeOfMonasticFoundation
Indicates the location where a monastic community or monastery was originally established or founded.
-
C.
monasticCommunityRelocatedTo
Indicates that a monastic community has moved its location from one place to another.
-
D.
monasticCenters
Indicates that one entity serves as a monastic center or hub for religious monastic life in relation to another entity.
-
E.
historicalEraOfMonastery
Indicates the historical era or period during which the monastery was founded, active, or most prominently associated.
- 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03e174c7c8190b04113f6529f5f0e |
completed | March 22, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69c0335b55a48190927a5b1529edb542 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:03 p.m.