Triple
T31841030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Isin |
E812802
|
entity |
| Predicate | usedWritingMaterial |
P125017
|
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: [Kingdom of Isin, usedWritingMaterial, clay tablets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWritingMaterial Context triple: [Kingdom of Isin, usedWritingMaterial, clay tablets]
-
A.
usedInWritingFor
Indicates that something (e.g., a tool, material, or medium) is employed as part of the process or context of writing for a particular purpose or audience.
-
B.
usedInWriting
chosen
Indicates that something (such as a tool, material, or medium) is employed as part of the process or act of writing.
-
C.
usesWriting
Indicates that one entity employs or applies a particular writing system, script, or written form for communication or representation.
-
D.
materialUsedInFiction
Indicates that a particular material (such as a substance or resource) is used, featured, or plays a role within a fictional work or narrative.
-
E.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6affbdda88190a9f53dc2550ca324 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:49 p.m.