Triple
T8953726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaneš |
E213419
|
entity |
| Predicate | materialFind |
P78356
|
FINISHED |
| Object | cuneiform tablets |
—
|
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: cuneiform tablets | Statement: [Kaneš, materialFind, cuneiform tablets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialFind Context triple: [Kaneš, materialFind, cuneiform tablets]
-
A.
materialFound
chosen
Indicates that a particular material is present, discovered, or detected in association with a specified entity or location.
-
B.
featuresMaterialFrom
Indicates that one entity incorporates, contains, or is composed of material originating from another entity.
-
C.
material
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
-
D.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
E.
materialSource
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670f88d0819085d7308a5cf6c764 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7 p.m.