Triple
T37688644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Purandar (1665) |
E938441
|
entity |
| Predicate | involvedGeneral |
P1256
|
FINISHED |
| Object | Jai Singh I |
—
|
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: Jai Singh I | Statement: [Treaty of Purandar (1665), involvedGeneral, Jai Singh I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedGeneral Context triple: [Treaty of Purandar (1665), involvedGeneral, Jai Singh I]
-
A.
oftenInvolvedWith
Indicates that one entity frequently participates in or is commonly associated with activities, events, or situations involving another entity.
-
B.
involves
chosen
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
C.
constantInvolved
Indicates that a constant participates in or is directly involved in the specified relation, operation, or context.
-
D.
isGenerally
Indicates that something holds or applies in most cases or under typical conditions, rather than in all specific instances.
-
E.
stillInvolvedIn
Indicates that an entity continues to participate in or be associated with a particular activity, role, or relationship at the present time.
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: May 3, 2026, 4:18 p.m.