Triple
T25261020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Московский журнал |
E633303
|
entity |
| Predicate | ориентация |
P158074
|
FINISHED |
| Object | светская словесность |
—
|
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: светская словесность | Statement: [Московский журнал, ориентация, светская словесность]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ориентация Context triple: [Московский журнал, ориентация, светская словесность]
-
A.
orientation
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
-
B.
orientationType
Indicates the specific kind or category of orientation relationship that exists between entities (such as spatial, directional, or alignment-based orientation).
-
C.
orientationPrinciple
Indicates the guiding rule or standard that directs how something is positioned, aligned, or oriented in relation to other things.
-
D.
orientedFrom
Indicates that one entity has a defined direction or orientation starting at or determined by another reference entity.
-
E.
orientadoA
Indicates that something is directed, aimed, or oriented toward a particular target, goal, or reference.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f483935ecc8190979f4ad83b192919 |
completed | May 1, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 1:13 p.m.