Triple
T30986347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodoros II of Alexandria |
E789536
|
entity |
| Predicate | monkSince |
P170883
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [Theodoros II of Alexandria, monkSince, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monkSince Context triple: [Theodoros II of Alexandria, monkSince, 1986]
-
A.
wasMonkOf
Indicates that a person was a member or monk belonging to a particular religious order, monastery, or monastic community.
-
B.
typeOfMonk
Indicates that one entity is a specific kind or category of monk in relation to another entity.
-
C.
relationshipToMonk
Indicates the specific type of relationship an entity has to a monk, such as familial, social, or institutional connection.
-
D.
yearsAsMonk
Indicates the number of years an entity has spent living as a monk.
-
E.
notableMonk
Indicates that a person is recognized as a monk of particular significance, prominence, or historical importance.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:56 p.m.