Triple
T6826576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine neumatic notation |
E157029
|
entity |
| Predicate | writtenLanguageContext |
P8383
|
FINISHED |
| Object | Greek |
—
|
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: Greek | Statement: [Byzantine neumatic notation, writtenLanguageContext, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenLanguageContext Context triple: [Byzantine neumatic notation, writtenLanguageContext, Greek]
-
A.
writesLanguage
Indicates that an entity produces written content in a particular language.
-
B.
originalLanguageContext
Indicates the language in which something was first created or expressed, providing the original linguistic context for its content or meaning.
-
C.
languageOfWritings
Indicates that a specified language is the one in which certain writings or written works are composed.
-
D.
writingSystemScope
Indicates the range or extent of content, languages, or contexts to which a particular writing system applies or is used.
-
E.
hasLanguageContext
chosen
Indicates that an entity is associated with or interpreted within a specific language or linguistic context.
- 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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d58375248190935dd38d618994e3 |
completed | March 27, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.