Triple
T16214193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | historic city of Asyut |
E393542
|
entity |
| Predicate | languageOfHistoricalInscriptions |
P30358
|
FINISHED |
| Object | Ancient 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: Ancient Egyptian | Statement: [historic city of Asyut, languageOfHistoricalInscriptions, Ancient Egyptian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfHistoricalInscriptions Context triple: [historic city of Asyut, languageOfHistoricalInscriptions, Ancient Egyptian]
-
A.
officialLanguageOfInscriptions
Indicates the language officially used in the inscriptions associated with a particular entity.
-
B.
secondaryLanguageOfInscriptions
Indicates that a specified language serves as the secondary language used in the inscriptions associated with a given entity.
-
C.
inscriptionsLanguage
Indicates that the language used in the inscriptions on an object or surface is the specified language.
-
D.
languageOfHistoricalRecord
chosen
Indicates the language in which a given historical record is written or recorded.
-
E.
ancientLanguages
Indicates that the related entities are languages that originated in and were used during ancient historical periods.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f393e08190be93400d754f0a2d |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.