Triple
T6442878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S3 (Gardiner sign list) |
E138266
|
entity |
| Predicate | phoneticType |
P20257
|
FINISHED |
| Object | uniliteral sign |
—
|
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: uniliteral sign | Statement: [S3 (Gardiner sign list), phoneticType, uniliteral sign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phoneticType Context triple: [S3 (Gardiner sign list), phoneticType, uniliteral sign]
-
A.
phoneticValue
Indicates a relationship where a symbol, sign, or written element is associated with the specific sound or sequence of sounds it represents.
-
B.
isPhonetic
Indicates that one entity represents the phonetic (sound-based) form or pronunciation of another entity.
-
C.
phoneticComponents
chosen
Indicates that one entity serves as a phonetic component or contributes to the pronunciation of another entity.
-
D.
phoneticProcess
Indicates a relationship where one sound or sequence of sounds undergoes a systematic phonetic change or transformation in a particular linguistic context.
-
E.
hasPhonologicalType
Indicates that one entity is characterized by or classified as having a particular phonological type (e.g., in terms of sound structure or phonological category).
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698b030481908b7bb4e16a8b3339 |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.