Triple
T32085222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tasua |
E819420
|
entity |
| Predicate | devotionalTexts |
P140517
|
FINISHED |
| Object | Marsiya (elegiac poetry) |
—
|
NE NERFINISHED |
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: Marsiya (elegiac poetry) | Statement: [Tasua, devotionalTexts, Marsiya (elegiac poetry)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devotionalTexts Context triple: [Tasua, devotionalTexts, Marsiya (elegiac poetry)]
-
A.
devotionalPoets
Indicates a relationship in which poets are characterized by or associated with devotional (religious or spiritual) themes in their work.
-
B.
devotionalCollection
chosen
Indicates that one entity is a curated set or compilation of devotional items, works, or practices associated with another entity.
-
C.
isDevotional
Indicates that something is intended for or characterized by religious worship, reverence, or spiritual devotion.
-
D.
devotionalElement
Indicates a relationship where something serves as or functions as an element used in devotional or religious practice.
-
E.
devotionalTitle
Indicates that one entity serves as the devotional or religiously themed title associated with 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b58ab03c81908e023cdc4dcb7919 |
completed | May 3, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:24 a.m.