Triple
T23625012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mushrif al-Din Saadi |
E583437
|
entity |
| Predicate | BustanForm |
P31757
|
FINISHED |
| Object | masnavi |
—
|
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: masnavi | Statement: [Mushrif al-Din Saadi, BustanForm, masnavi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BustanForm Context triple: [Mushrif al-Din Saadi, BustanForm, masnavi]
-
A.
formsBasis
Indicates that one entity serves as the foundational support, justification, or underlying principle upon which another entity is built, derived, or depends.
-
B.
stanzaForm
chosen
Indicates the specific structural pattern or arrangement of lines and verses used in a stanza.
-
C.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
D.
formsBypassOf
Indicates that one entity creates or constitutes an alternative route or channel that circumvents or avoids another entity or process.
-
E.
backForm
Indicates that an entity serves as a reverse, supporting, or rear-facing structure or configuration relative to another entity or form.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17c993c8190bf9ee3201869d240 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.