Triple
T32658081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Obelisk of Shalmaneser III |
E834918
|
entity |
| Predicate | depictsTributeFrom |
P91724
|
FINISHED |
| Object | Israel |
—
|
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: Israel | Statement: [Black Obelisk of Shalmaneser III, depictsTributeFrom, Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsTributeFrom Context triple: [Black Obelisk of Shalmaneser III, depictsTributeFrom, Israel]
-
A.
isPosthumousTributeTo
Indicates that something (such as a work, event, or honor) is created or given as a tribute to a person after that person has died.
-
B.
recordedTributeFrom
chosen
Indicates that one entity documented or registered the receipt of tribute from another entity.
-
C.
typeOfTribute
Indicates the specific kind or category of tribute that is being given or required in a relationship.
-
D.
subjectOfTribute
Indicates that one entity is the target or honoree of a tribute, such as a payment, offering, or act of respect made by another entity.
-
E.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 1:08 a.m.