Triple
T24649185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alphabetic Presentation Forms |
E610198
|
entity |
| Predicate | containsGlyphVariantsFor |
P84314
|
FINISHED |
| Object | Armenian letters |
—
|
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 letters | Statement: [Alphabetic Presentation Forms, containsGlyphVariantsFor, Armenian letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsGlyphVariantsFor Context triple: [Alphabetic Presentation Forms, containsGlyphVariantsFor, Armenian letters]
-
A.
hasGlyphsFor
chosen
Indicates that one entity provides or contains the necessary glyphs or visual symbols to represent another entity.
-
B.
hasKeyVariants
Indicates that an entity is associated with one or more alternative key forms or versions that function as variants of a primary key.
-
C.
hasGlyphRepertoireSize
Indicates the number of distinct glyphs included in an entity’s glyph repertoire.
-
D.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
E.
hasVariantText
Indicates that an entity is associated with an alternative or differing textual form of its content.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 18, 2026, 2:33 a.m.