Triple
T28808567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Code of Hammurabi stele |
E727445
|
entity |
| Predicate | depictionPosition |
P118773
|
FINISHED |
| Object | Hammurabi standing |
—
|
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: Hammurabi standing | Statement: [Code of Hammurabi stele, depictionPosition, Hammurabi standing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictionPosition Context triple: [Code of Hammurabi stele, depictionPosition, Hammurabi standing]
-
A.
positionDepicted
chosen
Indicates that one entity visually represents or depicts the spatial position or placement of another entity.
-
B.
depictionDetail
Indicates that one depiction provides additional detail, refinement, or a closer view of what is shown in another depiction.
-
C.
depictedNear
Indicates that two entities are shown in close spatial proximity to each other within the same depiction or scene.
-
D.
depictionElement
Indicates that one entity is an element or component that appears within the visual or representational depiction of another entity.
-
E.
depictionContext
Indicates the situational or environmental setting in which something is depicted or represented.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 28, 2026, 6:30 a.m.