Triple
T6297121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fustat |
E141156
|
entity |
| Predicate | earlierLanguage |
P28976
|
FINISHED |
| Object | Coptic |
—
|
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: Coptic | Statement: [Fustat, earlierLanguage, Coptic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierLanguage Context triple: [Fustat, earlierLanguage, Coptic]
-
A.
formerLanguage
chosen
Indicates that one entity was previously the language of another entity but is no longer in that role.
-
B.
languageIntroduced
Indicates that a particular language was brought into use or made known within a certain context, time, or place.
-
C.
parentLanguage
Indicates that one language is the ancestral or source language from which another language is derived or historically developed.
-
D.
languageOfEarliestForm
Indicates the language in which the earliest known form or attested version of something (e.g., a text, name, or expression) is recorded.
-
E.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
- 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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0643bd0748190af7abbebb6f94242 |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:27 p.m.