Triple
T36598518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abgar correspondence |
E902861
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legendary correspondence |
C41145
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: legendary correspondence Context triple: [Abgar correspondence, instanceOf, legendary correspondence]
-
A.
legendary pair
A legendary pair is a duo of individuals, creatures, or entities whose intertwined stories, complementary abilities, or iconic relationship elevate them to enduring mythic or cultural significance.
-
B.
legendary list
A legendary list is a curated collection of items, names, or events renowned for their exceptional significance, impact, or enduring fame.
-
C.
ancient letter
chosen
An ancient letter is a handwritten or inscribed message from antiquity, preserved on materials like papyrus, parchment, clay, or stone, conveying personal, administrative, or literary communication across time.
-
D.
legendary clan
A legendary clan is a storied lineage or group renowned across generations for extraordinary deeds, unique traditions, and enduring influence on history and myth.
-
E.
legendary cycle
A legendary cycle is a recurring sequence of mythic events or stories, often centered on heroic figures or divine interventions, that collectively form a cohesive narrative tradition within a culture.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:11 p.m.