Triple
T1859421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lobachevsky Prize |
E41779
|
entity |
| Predicate | fieldCategory |
P87
|
FINISHED |
| Object | science and technology awards |
—
|
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: science and technology awards | Statement: [Lobachevsky Prize, fieldCategory, science and technology awards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldCategory Context triple: [Lobachevsky Prize, fieldCategory, science and technology awards]
-
A.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
B.
fieldType
Indicates the classification or category that defines the nature or kind of a given field within a structure or context.
-
C.
fieldAdvanced
Indicates that a particular field or attribute has progressed beyond a basic or standard level, reflecting a more complex, specialized, or developed state.
-
D.
fieldName
Indicates the specific name or label assigned to a field within a data structure, form, or record.
-
E.
fieldPattern
Indicates a recurring or structured arrangement or configuration present within a field or area.
- 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_69a8864a83848190a4ec02721306c511 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb231de14819091da3a20ed03c430 |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafde4598819099d8229128348fd3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.