Triple
T22150421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golestān-e Saʿdī |
E547396
|
entity |
| Predicate | openingChapterTheme |
P147180
|
FINISHED |
| Object | conduct of kings |
—
|
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: conduct of kings | Statement: [Golestān-e Saʿdī, openingChapterTheme, conduct of kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingChapterTheme Context triple: [Golestān-e Saʿdī, openingChapterTheme, conduct of kings]
-
A.
openingVerseTheme
Indicates the primary idea or motif expressed in the opening verse of a text, song, or poem.
-
B.
openingTheme
Indicates that one entity serves as the opening theme (such as a song or musical piece) for another entity, typically a show, series, or similar work.
-
C.
openingThemeComposer
Indicates that the subject is the person who composed the musical opening theme for the specified work or production.
-
D.
openingThemeBasedOn
Indicates that the opening theme of a work is derived from, inspired by, or adapted from another specified source.
-
E.
openingThemePerformer
Indicates the performer or group responsible for performing the opening theme of a work (such as a TV show, film, or game).
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f37dac8190a7cecb12f4271515 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:33 p.m.