Triple
T21794510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriarch Meletius IV of Constantinople |
E538058
|
entity |
| Predicate | laterPost |
P129046
|
FINISHED |
| Object | Patriarch of Alexandria and All Africa |
—
|
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: Patriarch of Alexandria and All Africa | Statement: [Patriarch Meletius IV of Constantinople, laterPost, Patriarch of Alexandria and All Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPost Context triple: [Patriarch Meletius IV of Constantinople, laterPost, Patriarch of Alexandria and All Africa]
-
A.
laterPosting
chosen
Indicates that one posting, message, or publication occurs at a later time than another in a temporal sequence.
-
B.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
C.
laterTask
Indicates that one task occurs after another in time, representing a temporal ordering where the first task precedes the laterTask.
-
D.
laterFunction
Indicates that one function or event occurs after another in time.
-
E.
laterWork
Indicates that one work was created, published, or produced after another work in time.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0622329b08190b8cd9be714aca456 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.