Triple
T30168803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fara (ancient Shuruppak) |
E766862
|
entity |
| Predicate | yieldedArtifactType |
P162081
|
FINISHED |
| Object | clay 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: clay tablets | Statement: [Fara (ancient Shuruppak), yieldedArtifactType, clay tablets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yieldedArtifactType Context triple: [Fara (ancient Shuruppak), yieldedArtifactType, clay tablets]
-
A.
producedArtifactType
chosen
Indicates the type or category of artifact that is created or generated as the result of a production process or activity.
-
B.
hasTypeOfArtifact
Indicates that one entity is classified as, or belongs to, a particular type or category of artifact in relation to another entity.
-
C.
yieldedTaxon
Indicates that one entity produced, revealed, or resulted in the discovery or identification of a particular taxon.
-
D.
artifactType
Indicates the specific kind or category of artifact that an entity is classified as.
-
E.
artifactTypeFound
Indicates that a specific type of artifact has been discovered or identified in association with a given context or location.
- 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_69f67f0951288190a809554f58be124f |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:24 p.m.