Triple
T36598533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abgar correspondence |
E902861
|
entity |
| Predicate | claimedOriginalDate |
P13849
|
FINISHED |
| Object | 1st century |
—
|
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: 1st century | Statement: [Abgar correspondence, claimedOriginalDate, 1st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedOriginalDate Context triple: [Abgar correspondence, claimedOriginalDate, 1st century]
-
A.
claimed
Indicates that an entity has asserted or stated something as true, often without definitive proof or verification.
-
B.
firstClaimedBy
Indicates that the referenced entity was the first to assert ownership, discovery, or authorship of another entity.
-
C.
originallyProclaimed
Indicates that an entity first formally announced, declared, or made known another entity or statement at an earlier point in time.
-
D.
claimedFoundationDate
Indicates the date that an entity asserts or reports as its founding date, regardless of historical accuracy.
-
E.
claimedYear
chosen
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
- 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_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:11 p.m.