Triple
T9951641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suppiluliuma II |
E195343
|
entity |
| Predicate | inscriptionReports |
P1726
|
FINISHED |
| Object | victory over Alashiya |
—
|
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: victory over Alashiya | Statement: [Suppiluliuma II, inscriptionReports, victory over Alashiya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionReports Context triple: [Suppiluliuma II, inscriptionReports, victory over Alashiya]
-
A.
reportsWithin
Indicates that one entity submits or delivers a report to another entity within a specified time frame or boundary.
-
B.
reportsThrough
Indicates that one entity formally communicates and is accountable to another entity through an established reporting or supervisory chain.
-
C.
inscription
chosen
Indicates that text has been written, carved, or engraved onto a surface or object.
-
D.
reportsDecisionsOf
Indicates that one entity communicates or provides information about the decisions made by another entity.
-
E.
officiallyReports
Indicates that one entity formally provides information, updates, or accountability to another entity within an official or authorized reporting structure.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6922f888190b5c4b58fbe21bea2 |
completed | April 2, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:46 p.m.