Triple
T30164946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eshnunna |
E766768
|
entity |
| Predicate | hasArtifacts |
P89518
|
FINISHED |
| Object | statuettes |
—
|
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: statuettes | Statement: [Eshnunna, hasArtifacts, statuettes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtifacts Context triple: [Eshnunna, hasArtifacts, statuettes]
-
A.
hasSignificantArtifact
chosen
Indicates that an entity possesses or is associated with an artifact that is of notable importance, influence, or relevance within a given context.
-
B.
artifactsWere
Indicates that certain objects or creations functioned as artifacts in a particular context or time.
-
C.
hasCharacteristicArtifact
Indicates that an entity is associated with a specific artifact that characterizes, exemplifies, or is typical of it.
-
D.
hasArtFeature
Indicates that an entity possesses or is characterized by a particular artistic attribute, element, or stylistic feature.
-
E.
hasArtificialComponent
Indicates that an entity includes, contains, or is composed of at least one non-natural, human-made component.
- 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_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 29, 2026, 7:23 p.m.