Triple
T5759235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parvati Patil |
E127046
|
entity |
| Predicate | subjectInterest |
P66206
|
FINISHED |
| Object | Divination |
—
|
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: Divination | Statement: [Parvati Patil, subjectInterest, Divination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectInterest Context triple: [Parvati Patil, subjectInterest, Divination]
-
A.
primaryInterest
Indicates that one entity is the main or most significant focus of attention, concern, or engagement for another entity.
-
B.
collectorInterest
Indicates that one entity has a special interest in acquiring, owning, or seeking out another entity as part of a collection.
-
C.
recognizedInterest
Indicates that one entity has formally acknowledged or identified another entity’s interest in something as valid or relevant.
-
D.
publicInterestStatus
Indicates that something has been evaluated or designated in terms of its relevance, importance, or impact to the general public or society at large.
-
E.
representsInterestOf
Indicates that one entity expresses, holds, or embodies an interest, concern, or stake in another entity or subject.
- F. None of above. chosen
Provenance (4 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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0293771ec8190a0082685327d649b |
completed | March 22, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028fec2bc819083f5dca6a8d9d435 |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:49 p.m.