Triple
T28445167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian |
E715820
|
entity |
| Predicate | hasAspectualVerbSystem |
P5214
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Russian, hasAspectualVerbSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAspectualVerbSystem Context triple: [Russian, hasAspectualVerbSystem, yes]
-
A.
hasVerbAspect
Indicates that a verb or verbal expression is associated with a particular grammatical aspect (such as perfective, imperfective, or progressive) describing the temporal structure of the action or state.
-
B.
hasTenseAspectSystem
chosen
Indicates that a language or clause employs a particular system for expressing tense and aspect distinctions.
-
C.
hasTenseAspect
Indicates that a verb or clause is associated with a specific grammatical tense and aspect configuration.
-
D.
hasLanguageAspect
Indicates that an entity is associated with a particular linguistic aspect, such as tense, mood, or grammatical feature, in relation to a language.
-
E.
hasTenseAspectMoodMarkers
Indicates that an expression includes explicit markers specifying its tense, aspect, and/or mood.
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 1:48 a.m.