Triple
T28535718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suppiluliuma I |
E722155
|
entity |
| Predicate | sentSon |
P164620
|
FINISHED |
| Object | Zannanza |
—
|
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: Zannanza | Statement: [Suppiluliuma I, sentSon, Zannanza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentSon Context triple: [Suppiluliuma I, sentSon, Zannanza]
-
A.
sentAs
Indicates that one entity was transmitted, dispatched, or delivered in the form, role, or capacity of another (e.g., an item or message being sent as something specific).
-
B.
sentAfter
Indicates that one message or item was sent at a later time than another specified message or item.
-
C.
sentSignalTo
Indicates that one entity transmitted a signal or message to another entity.
-
D.
sentSignalFrom
Indicates that one entity transmitted or emitted a signal originating from a specified source entity.
-
E.
sentWhen
Indicates the time or temporal context at which a message, item, or communication was sent.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fda797081909e259eb25d51e206 |
completed | May 2, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 3:31 a.m.