Triple
T30574212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Пепел |
E778198
|
entity |
| Predicate | социальныйСтатус |
P62272
|
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.
subjectSocialStatus
chosen
Indicates the social standing or rank that the subject holds within a society or group.
-
B.
possibleSocialStatus
Indicates that one entity may hold, attain, or be associated with a particular social status in relation to another context or system.
-
C.
civicStatus
Indicates the legal or social standing of an individual within a civic or societal framework, such as marital or citizenship status.
-
D.
protagonistSocialStatus
Indicates the social standing or class position held by the story’s main character in relation to others in their society.
-
E.
civilStatus
Indicates the legal marital or family-related status of a person (e.g., single, married, divorced, widowed) at a given time.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:22 p.m.