Triple
T28497427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zvartnots Cathedral archaeological site |
E721143
|
entity |
| Predicate | usedLanguageOfInscriptions |
P15804
|
FINISHED |
| Object | Armenian |
—
|
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: Armenian | Statement: [Zvartnots Cathedral archaeological site, usedLanguageOfInscriptions, Armenian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedLanguageOfInscriptions Context triple: [Zvartnots Cathedral archaeological site, usedLanguageOfInscriptions, Armenian]
-
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
chosen
Indicates that the language used in the inscriptions on an object or surface is the specified language.
-
D.
ancientLanguages
Indicates that the related entities are languages that originated in and were used during ancient historical periods.
-
E.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f40815c8190862801e861a1f578 |
completed | May 2, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:04 a.m.