Triple
T35713203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudin |
E1031925
|
entity |
| Predicate | socialClassOfProtagonist |
P33359
|
FINISHED |
| Object | Russian nobility |
—
|
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: Russian nobility | Statement: [Rudin, socialClassOfProtagonist, Russian nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialClassOfProtagonist Context triple: [Rudin, socialClassOfProtagonist, Russian nobility]
-
A.
socialClassPosition
Indicates the relative social status or rank an entity holds within a social hierarchy or class structure.
-
B.
socialClassSystem
Indicates a hierarchical organization of people into social classes based on status, power, or economic position.
-
C.
socialClassAspiration
Indicates a desire or intention by one entity to attain a higher or different social class or status than its current one.
-
D.
protagonistSocialStatus
chosen
Indicates the social standing or class position held by the story’s main character in relation to others in their society.
-
E.
socialClassAtStart
Indicates the social class or socioeconomic status an entity belongs to at the beginning of a specified period, event, or process.
- 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:05 p.m.