Triple
T3420805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macedonian |
E72109
|
entity |
| Predicate | hasGlagoliticTradition |
P48602
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Macedonian, hasGlagoliticTradition, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlagoliticTradition Context triple: [Macedonian, hasGlagoliticTradition, no]
-
A.
usesPrimaryLiturgicalLanguageHistorically
Indicates that an entity has historically used a particular primary liturgical language in its religious rites or worship practices.
-
B.
isFirstSlavicLiteraryLanguage
Indicates that the subject language is recognized as the earliest established literary language among the Slavic languages.
-
C.
hasSourceTradition
Indicates that something originates from, or is derived within, a particular cultural, religious, intellectual, or historical tradition.
-
D.
hasTraditionalDialect
Indicates that an entity possesses or is associated with a traditional form or variety of a language or dialect.
-
E.
hasLinguisticHeritage
Indicates that one entity possesses or is associated with the linguistic background, tradition, or ancestry of another entity.
- F. None of above. chosen
Provenance (4 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb94eb9e8819087a525df4550914b |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfea024819094b41a13bc004bda |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb00f4f8c81908f88daf71f6a9c29 |
completed | March 8, 2026, 5:21 p.m. |
Created at: March 8, 2026, 3:15 p.m.