Triple
T22162282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betal Panchabinsati |
E547699
|
entity |
| Predicate | questionAnswerPattern |
P79744
|
FINISHED |
| Object | riddle posed at end of each tale |
—
|
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: riddle posed at end of each tale | Statement: [Betal Panchabinsati, questionAnswerPattern, riddle posed at end of each tale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questionAnswerPattern Context triple: [Betal Panchabinsati, questionAnswerPattern, riddle posed at end of each tale]
-
A.
questionFormulation
Indicates that one entity formulates, poses, or expresses a question directed toward another entity or context.
-
B.
typicalQuestion
Indicates that an entity is a common or standard question typically asked in a given context or situation.
-
C.
typicalAnswerType
Indicates the usual or expected kind of entity or value that serves as an answer to a given question or query.
-
D.
questionConveyedBy
chosen
Indicates that a particular question is expressed, communicated, or represented by a given medium, message, or artifact.
-
E.
questionType
Indicates the specific category or kind of question that an item, query, or prompt belongs to.
- 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_69e11e3c4c5c81908d336165816b12e0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a2e47a88190a3b5c05398605f68 |
completed | April 28, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69e71b41555881909b8e22718974d527 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:34 p.m.