Triple
T32070655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lipit-Ishtar |
E819001
|
entity |
| Predicate | hasGenreInscriptions |
P124610
|
FINISHED |
| Object | royal hymns |
—
|
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: royal hymns | Statement: [Lipit-Ishtar, hasGenreInscriptions, royal hymns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenreInscriptions Context triple: [Lipit-Ishtar, hasGenreInscriptions, royal hymns]
-
A.
hasGivenGenre
Indicates that an entity is associated with a specific genre that has been assigned or designated to it.
-
B.
hasGenreRelation
chosen
Indicates that there is an association between an entity and a specific genre, specifying the type or category it belongs to.
-
C.
hasGenreInPortfolio
Indicates that an entity (such as a creator, label, or catalog) includes a particular genre within its body of work or offerings.
-
D.
hasTargetGenreCategory
Indicates that something is associated with or classified under a specific target genre category.
-
E.
hasGenreFeature
Indicates that something possesses a characteristic, element, or trait associated with a particular genre.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 1, 2026, 12:23 a.m.