Triple
T1778374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simonopetra Monastery |
E39231
|
entity |
| Predicate | subjectToRule |
P1313
|
FINISHED |
| Object | Athonite charter and typikon |
—
|
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: Athonite charter and typikon | Statement: [Simonopetra Monastery, subjectToRule, Athonite charter and typikon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToRule Context triple: [Simonopetra Monastery, subjectToRule, Athonite charter and typikon]
-
A.
isSubjectTo
chosen
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
B.
associatedWithRule
Indicates that an entity is linked or connected to a specific rule, such as being governed, constrained, or defined by that rule.
-
C.
isRuleGoverned
Indicates that an entity’s behavior, structure, or operation is determined and constrained by explicit rules or formal regulations.
-
D.
usesRulesFrom
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
E.
compositionRule
Indicates how multiple elements or components are combined or arranged according to a specific rule or pattern.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.