Triple
T1983722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coptic Orthodox Church |
E43089
|
entity |
| Predicate | heritageLanguageBranch |
P6149
|
FINISHED |
| Object | Egyptian language |
—
|
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: Egyptian language | Statement: [Coptic Orthodox Church, heritageLanguageBranch, Egyptian language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageLanguageBranch Context triple: [Coptic Orthodox Church, heritageLanguageBranch, Egyptian language]
-
A.
heritageLanguage
chosen
Indicates that one entity is the ancestral or culturally inherited language associated with another entity.
-
B.
hasLinguisticHeritage
Indicates that one entity possesses or is associated with the linguistic background, tradition, or ancestry of another entity.
-
C.
languageFamilyBranchOf
Indicates that one language family branch is a sub-group or subdivision within a larger language family.
-
D.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
-
E.
heritageLanguageShift
Indicates a change over time in which a community or individual moves away from using their ancestral or heritage language toward another dominant language.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb96f932881908bebfc4176fda7c0 |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb798d288819083132cf14605bd02 |
completed | March 7, 2026, 5:28 a.m. |
Created at: March 4, 2026, 7:37 p.m.