Triple
T1515531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ugaritic alphabet |
E32109
|
entity |
| Predicate | writingTechnique |
P14965
|
FINISHED |
| Object | cuneiform wedge impressions |
—
|
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 wedge impressions | Statement: [Ugaritic alphabet, writingTechnique, cuneiform wedge impressions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingTechnique Context triple: [Ugaritic alphabet, writingTechnique, cuneiform wedge impressions]
-
A.
writingTool
Indicates that one entity serves as a tool or instrument used by another entity for the act of writing.
-
B.
narrativeStyle
Indicates how a narrative is told, such as the point of view, tone, and structural approach used to present a story or account.
-
C.
writingTradition
Indicates a relationship where an entity is associated with, follows, or belongs to a particular system or style of written expression or script usage.
-
D.
rite
Indicates a ceremonial or ritual action performed according to established traditions or religious practices.
-
E.
artisticTechnique
chosen
Indicates the method, style, or process used to create or execute an artistic work.
- 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_69a885e8caf88190a5fbb6159ce87786 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9396e16408190b5e7b0ac43376d81 |
completed | March 5, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69a907aa67cc81909f00135365447399 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.