Triple
T30321478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian Athonite monastic community |
E771211
|
entity |
| Predicate | foundingOfIvironMonastery |
P52045
|
FINISHED |
| Object | c. 980 |
—
|
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: c. 980 | Statement: [Georgian Athonite monastic community, foundingOfIvironMonastery, c. 980]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingOfIvironMonastery Context triple: [Georgian Athonite monastic community, foundingOfIvironMonastery, c. 980]
-
A.
numberOfMonasteriesFounded
Indicates the total count of monasteries that a given entity has established or founded.
-
B.
placeOfMonasticFoundation
Indicates the location where a monastic community or monastery was originally established or founded.
-
C.
founderOfMonastery
Indicates that a person established or founded a particular monastery.
-
D.
monasticTraditionFoundedInYear
Indicates that a particular monastic tradition was established or came into existence in a specified year.
-
E.
monasteryEstablished
chosen
Indicates that a monastery was founded or formally established at a particular time, place, or by a specific agent.
- 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 29, 2026, 7:52 p.m.