Triple
T30170092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Year festival in Babylon |
E766895
|
entity |
| Predicate | kingRole |
P41822
|
FINISHED |
| Object | ritual humiliation before Marduk |
—
|
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: ritual humiliation before Marduk | Statement: [New Year festival in Babylon, kingRole, ritual humiliation before Marduk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kingRole Context triple: [New Year festival in Babylon, kingRole, ritual humiliation before Marduk]
-
A.
roleInKingship
chosen
Indicates that an entity holds or plays a specific role or position within a system of kingship or royal authority.
-
B.
kingOf
Indicates that one entity holds the position or role of king in relation to another entity, typically a territory, people, or domain.
-
C.
monarchRole
Indicates that an entity holds or is assigned the role, office, or position of a monarch in relation to a state or domain.
-
D.
monarchicalRole
Indicates that one entity holds or is assigned a specific position, function, or office within a monarchical system of governance.
-
E.
mainKingCharacter
Indicates that the entity serves as the primary king character or central royal protagonist in a given context.
- 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_69f67f0b25908190baf7f9dfef6ec6ce |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:24 p.m.