Triple
T36621262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tushratta |
E904043
|
entity |
| Predicate | sourceOfLetters |
P173462
|
FINISHED |
| Object | Amarna letters |
—
|
NE NERFINISHED |
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: Amarna letters | Statement: [Tushratta, sourceOfLetters, Amarna letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceOfLetters Context triple: [Tushratta, sourceOfLetters, Amarna letters]
-
A.
writesLettersTo
Indicates that one entity composes and sends letters directed to another entity.
-
B.
settingOfManyLetters
Indicates a setting or context in which many letters (such as written messages or characters) occur, are exchanged, or are central to the situation.
-
C.
letterer
Indicates that one entity serves as the letterer of another, typically responsible for drawing or designing the lettering (such as text or captions) in that work.
-
D.
letterWrittenFrom
chosen
Indicates that a letter is authored at or sent from a particular origin location or source entity.
-
E.
lettersWrittenBetween
Indicates that letters have been written and exchanged between the two entities, reflecting a mutual correspondence.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.