Triple
T9517936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohairic Coptic |
E229571
|
entity |
| Predicate | hasAdditionalLettersFrom |
P9187
|
FINISHED |
| Object | Demotic Egyptian signs |
—
|
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 signs | Statement: [Bohairic Coptic, hasAdditionalLettersFrom, Demotic Egyptian signs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdditionalLettersFrom Context triple: [Bohairic Coptic, hasAdditionalLettersFrom, Demotic Egyptian signs]
-
A.
hasAdditionalLetters
chosen
Indicates that one entity contains extra or more letters than another entity, beyond a specified base set or reference.
-
B.
usesAdditionalLettersFrom
Indicates that one entity forms or derives its representation by incorporating extra letters taken from another entity beyond those originally present.
-
C.
hasLettersFor
Indicates that one entity possesses or contains written correspondence intended for another entity.
-
D.
hasLetter
Indicates that one entity contains, includes, or is associated with a specific letter or character.
-
E.
hasLetterBy
Indicates that an entity possesses or is associated with a letter authored or sent by 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9880417c819097dde277988df36d |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:59 p.m.