Triple
T37688662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Purandar (1665) |
E938441
|
entity |
| Predicate | requiredMilitaryServiceBy |
P46563
|
FINISHED |
| Object | Shivaji |
—
|
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: Shivaji | Statement: [Treaty of Purandar (1665), requiredMilitaryServiceBy, Shivaji]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredMilitaryServiceBy Context triple: [Treaty of Purandar (1665), requiredMilitaryServiceBy, Shivaji]
-
A.
hadMilitaryObligationsTo
chosen
Indicates that one party was bound by duty or law to provide military service, support, or protection to another party.
-
B.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
-
C.
stanceOnMilitaryService
Indicates an entity’s expressed position, attitude, or policy regarding military service.
-
D.
conscriptionAppliesTo
Indicates that mandatory military service requirements are imposed on, or are applicable to, a particular person or group.
-
E.
hasMilitaryStatus
Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
- 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_6a009273634c8190b5b9c87053b56760 |
completed | May 10, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_6a0092171230819096e4274dd97e0410 |
completed | May 10, 2026, 2:11 p.m. |
Created at: May 3, 2026, 4:18 p.m.