Triple
T31666715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memphitic Coptic |
E808144
|
entity |
| Predicate | scriptAdditionalCharactersFrom |
P10533
|
FINISHED |
| Object | Demotic Egyptian |
—
|
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: Demotic Egyptian | Statement: [Memphitic Coptic, scriptAdditionalCharactersFrom, Demotic Egyptian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptAdditionalCharactersFrom Context triple: [Memphitic Coptic, scriptAdditionalCharactersFrom, Demotic Egyptian]
-
A.
providesAdditionalCharactersFor
Indicates that one entity supplies extra or supplementary characters to be used by another entity or process.
-
B.
usesAdditionalLettersFrom
chosen
Indicates that one entity forms or derives its representation by incorporating extra letters taken from another entity beyond those originally present.
-
C.
characterAcquisition
Indicates the relationship in which an entity comes to possess, gain, or obtain a character, trait, or attribute.
-
D.
allyOfCharacter
Indicates that one character maintains an alliance or supportive partnership with another character.
-
E.
contributesCharacter
Indicates that one entity adds or provides a particular character or trait to 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 30, 2026, 10:59 p.m.