Triple
T20279431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Works of Evagrius Ponticus |
E503098
|
entity |
| Predicate | receivedIn |
P139521
|
FINISHED |
| Object | Eastern Orthodox tradition |
—
|
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: Eastern Orthodox tradition | Statement: [Works of Evagrius Ponticus, receivedIn, Eastern Orthodox tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedIn Context triple: [Works of Evagrius Ponticus, receivedIn, Eastern Orthodox tradition]
-
A.
receivedFor
Indicates that something was obtained, accepted, or taken into possession on behalf of or for the benefit of a specified entity.
-
B.
receivedTransmissionOf
Indicates that one entity has obtained or been sent a transmission (such as a message, signal, or data) originating from another entity.
-
C.
receivedSign
Indicates that one entity has obtained or been given a sign (such as a signal, symbol, or indication) from another entity.
-
D.
receivedForWork
Indicates that something was obtained or accepted as compensation or reward in exchange for performing work or services.
-
E.
receivedDocument
Indicates that one entity has been given and taken possession of a document from another entity or source.
- 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_69e0b4b0e79c8190bd61f22ef1329fa8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6768ddfd0819098b2cc7fed0f4fe2 |
completed | April 20, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 10:36 a.m.