Triple
T24878198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Draupadi with strong devotional traits |
E622630
|
entity |
| Predicate | interpretsEventAs |
P113548
|
FINISHED |
| Object | test of faith |
—
|
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: test of faith | Statement: [Draupadi with strong devotional traits, interpretsEventAs, test of faith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interpretsEventAs Context triple: [Draupadi with strong devotional traits, interpretsEventAs, test of faith]
-
A.
interpretsEvent
Indicates that an entity analyzes and assigns meaning or significance to an event.
-
B.
treatsEventsAs
chosen
Indicates that one entity regards, handles, or interprets certain occurrences or inputs specifically as events, typically for the purpose of processing, categorization, or response.
-
C.
discriminatesEventsBy
Indicates a relationship where one entity distinguishes or separates events based on certain criteria or characteristics.
-
D.
impliesEvent
Indicates that one event logically leads to, entails, or guarantees the occurrence of another event.
-
E.
representsInEvent
Indicates that an entity serves as a representative or proxy for another entity within the context of a specific event.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 5:24 a.m.