Triple
T21108348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heer |
E520109
|
entity |
| Predicate | centralWorkForm |
P36545
|
FINISHED |
| Object | qissa (romantic epic poem) |
—
|
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: qissa (romantic epic poem) | Statement: [Heer, centralWorkForm, qissa (romantic epic poem)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralWorkForm Context triple: [Heer, centralWorkForm, qissa (romantic epic poem)]
-
A.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
B.
centralProject
Indicates that one project serves as the primary or core project around which other related projects or activities are organized.
-
C.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
D.
formOfWork
chosen
Indicates that one creative work is a specific form, version, or expression of another related work.
-
E.
formsCenterOf
Indicates that one entity constitutes the central or core part of another entity.
- 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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e720ffa998819082db225363ac3b23 |
completed | April 21, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:54 p.m.