Triple
T29062978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alphabet Park near Oshakan |
E735589
|
entity |
| Predicate | alphabetHonored |
P165970
|
FINISHED |
| Object | Armenian alphabet |
—
|
NE NERFINISHED |
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 alphabet | Statement: [Alphabet Park near Oshakan, alphabetHonored, Armenian alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alphabetHonored Context triple: [Alphabet Park near Oshakan, alphabetHonored, Armenian alphabet]
-
A.
alphabet
Indicates that one entity is an alphabet or set of symbols used for representing elements (such as characters or tokens) in relation to another entity.
-
B.
alphabetType
Indicates the type or classification of an alphabet used by a writing system or language.
-
C.
alphabetic
Indicates that the characters in a string or sequence consist solely of letters from an alphabet, with no digits or special symbols.
-
D.
alphabeticStatus
Indicates the relative ordering or position of entities based on alphabetical sequence.
-
E.
alphabetRange
Indicates that one entity specifies a contiguous range of letters in an alphabet that extends from the starting letter to the ending letter.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66098d5dc81909bfa2025bdd09d99 |
completed | May 2, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65ad638ac8190a17bb987fce53279 |
completed | May 2, 2026, 8:13 p.m. |
Created at: April 28, 2026, 10:16 a.m.