Triple
T37688665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Purandar (1665) |
E938441
|
entity |
| Predicate | requiredShivajiToAttend |
P86851
|
FINISHED |
| Object | Mughal court at Agra |
—
|
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: Mughal court at Agra | Statement: [Treaty of Purandar (1665), requiredShivajiToAttend, Mughal court at Agra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredShivajiToAttend Context triple: [Treaty of Purandar (1665), requiredShivajiToAttend, Mughal court at Agra]
-
A.
mayAttend
Indicates that an entity is permitted or eligible to be present at or participate in a particular event, activity, or gathering.
-
B.
celebrationRequires
Indicates that a particular celebration depends on or necessitates the presence, occurrence, or provision of something.
-
C.
requiredTributeTo
Indicates that one entity is obligated to provide a tribute or payment to another entity.
-
D.
requiresParticipationOf
chosen
Indicates that one entity’s occurrence, validity, or completion depends on the active involvement or participation of another entity.
-
E.
laterAttends
Indicates that one entity attends an event or place at a time later than another referenced attendance.
- 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_6a009f53a4948190aef4ede1713e1748 |
completed | May 10, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_6a009edc53d4819080b22c1074a990f3 |
completed | May 10, 2026, 3:06 p.m. |
Created at: May 3, 2026, 4:18 p.m.