Triple
T36598528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abgar correspondence |
E902861
|
entity |
| Predicate | traditionallyPreservedIn |
P193745
|
FINISHED |
| Object | Syriac 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: Syriac tradition | Statement: [Abgar correspondence, traditionallyPreservedIn, Syriac tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyPreservedIn Context triple: [Abgar correspondence, traditionallyPreservedIn, Syriac tradition]
-
A.
traditionallyFoundIn
Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
-
B.
preservedWork
chosen
Indicates that one entity has been kept, maintained, or conserved so that another entity (often in the present) can still access, use, or benefit from it.
-
C.
traditionallyUsedBy
Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
-
D.
traditionallyFor
Indicates that something is customarily used, intended, or associated with a particular purpose, group, event, or context according to tradition.
-
E.
regionOfPreservation
Indicates the specific area or portion of an object or specimen where preservation has occurred or is observed.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: May 3, 2026, 4:11 p.m.