Triple
T34121947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lomavren |
E875162
|
entity |
| Predicate | hasGrammaticalBase |
P100968
|
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: [Lomavren, hasGrammaticalBase, Armenian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrammaticalBase Context triple: [Lomavren, hasGrammaticalBase, Armenian]
-
A.
hasMorphosyntacticBasis
Indicates that one linguistic element’s form or syntactic behavior is grounded in, derived from, or systematically determined by another element’s morphosyntactic properties.
-
B.
hasMorphologicalBase
Indicates that one linguistic form is derived from, or structurally based on, another underlying morphological form.
-
C.
primaryGrammaticalBasis
Indicates that one element serves as the main grammatical foundation or core structure upon which another linguistic element is based or constructed.
-
D.
hasGrammar
Indicates that an entity possesses, follows, or is associated with a particular system of grammatical rules or structure.
-
E.
hasGrammarFrom
chosen
Indicates that one entity derives or uses its grammatical structure or rules from another entity.
- 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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 1:53 a.m.