Triple
T4836168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Draupadi |
E108063
|
entity |
| Predicate | incognitoService |
P9325
|
FINISHED |
| Object | maid to Queen Sudeshna of Virata |
—
|
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: maid to Queen Sudeshna of Virata | Statement: [Draupadi, incognitoService, maid to Queen Sudeshna of Virata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incognitoService Context triple: [Draupadi, incognitoService, maid to Queen Sudeshna of Virata]
-
A.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used by another entity.
-
B.
serviceOf
chosen
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
C.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
D.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
E.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.