Triple
T28098263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naram-Sin Victory Stele |
E710157
|
entity |
| Predicate | usesArtisticDevice |
P84366
|
FINISHED |
| Object | hierarchical scale |
—
|
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: hierarchical scale | Statement: [Naram-Sin Victory Stele, usesArtisticDevice, hierarchical scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesArtisticDevice Context triple: [Naram-Sin Victory Stele, usesArtisticDevice, hierarchical scale]
-
A.
hasArtisticStrategy
Indicates that an entity employs or is associated with a particular artistic approach, method, or plan in creating or presenting art.
-
B.
hasArtFeature
Indicates that an entity possesses or is characterized by a particular artistic attribute, element, or stylistic feature.
-
C.
hasArtisticContent
Indicates that something contains or embodies artistic material, expression, or creative work.
-
D.
artUse
chosen
Indicates that one entity uses, applies, or employs another entity within an artistic or creative context.
-
E.
usedForArtisticPurpose
Indicates that something is employed or applied with the intention of creating, expressing, or enhancing art or aesthetic experience.
- 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_69ef9b70fd108190a875953b2e50ca91 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 9:03 p.m.