Triple
T30164999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mursili I |
E766769
|
entity |
| Predicate | approximateDateOfBabylonCampaign |
P185194
|
FINISHED |
| Object | late 17th or early 16th century BCE |
—
|
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: late 17th or early 16th century BCE | Statement: [Mursili I, approximateDateOfBabylonCampaign, late 17th or early 16th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDateOfBabylonCampaign Context triple: [Mursili I, approximateDateOfBabylonCampaign, late 17th or early 16th century BCE]
-
A.
timeOfAssyrianConquest
Indicates the point in time at which the Assyrian conquest of a given entity occurred.
-
B.
resultOfAssyrianCampaign
Indicates that something occurs as a consequence or outcome of a specific Assyrian military campaign.
-
C.
approximateBattleDate
chosen
Indicates that the associated date is an estimated or approximate time when the battle occurred, rather than an exact, confirmed date.
-
D.
timeToFallOfBaghdad
Indicates the duration of time remaining until the fall of Baghdad occurs.
-
E.
yearOfHannibalAttack
Indicates the specific year in which Hannibal carried out the referenced attack or military campaign.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: April 29, 2026, 7:23 p.m.