Triple
T4817018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praskovya Fyodorovna |
E107611
|
entity |
| Predicate | seeksFromIvanIlyich |
P59824
|
FINISHED |
| Object | social advancement |
—
|
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: social advancement | Statement: [Praskovya Fyodorovna, seeksFromIvanIlyich, social advancement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeksFromIvanIlyich Context triple: [Praskovya Fyodorovna, seeksFromIvanIlyich, social advancement]
-
A.
seventhStation
Indicates that one entity is the seventh stop, stage, or position in an ordered sequence of stations relative to another.
-
B.
soughtPassage
Indicates that one entity attempted to obtain or gain access to a particular passage, route, or way through something.
-
C.
seeksRedemption
Indicates that an entity is actively striving to atone for past wrongs or failures and restore its moral standing.
-
D.
soughtTo
Indicates that one entity attempted or intended to obtain, achieve, or bring about another entity or outcome.
-
E.
liesBeyond
Indicates that one entity is located at a greater distance or outside the boundary of another reference point, region, or limit.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1dfa3481909d240d50ed0ee38c |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6dda5e808190a26ec85e4499d8e4 |
completed | March 20, 2026, 3:55 p.m. |
Created at: March 20, 2026, 1:24 p.m.