Triple
T16369220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mokhiniso Rakhimova |
E397518
|
entity |
| Predicate | spouseOfNotableWorkGenre |
P44007
|
FINISHED |
| Object | adventure fiction |
—
|
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: adventure fiction | Statement: [Mokhiniso Rakhimova, spouseOfNotableWorkGenre, adventure fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfNotableWorkGenre Context triple: [Mokhiniso Rakhimova, spouseOfNotableWorkGenre, adventure fiction]
-
A.
spouseNotableWorkField
Indicates that the notable work or professional field associated with a person’s spouse is being specified.
-
B.
spouseNotableWorkLanguage
Indicates that the notable work of a person's spouse is expressed or created in a particular language.
-
C.
genreAssociatedWithSpouse
chosen
Indicates that a particular genre is associated with, or characterizes, the spouse of the referenced entity.
-
D.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
E.
spouseAppearsIn
Indicates that the spouse of a given person appears or is featured in a specified work, context, or setting.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff4021e88190ad093bab74cf82a4 |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.