Triple
T37688658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Purandar (1665) |
E938441
|
entity |
| Predicate | stipulatedRevenueShareRegion |
P164478
|
FINISHED |
| Object | Konkan |
—
|
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: Konkan | Statement: [Treaty of Purandar (1665), stipulatedRevenueShareRegion, Konkan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stipulatedRevenueShareRegion Context triple: [Treaty of Purandar (1665), stipulatedRevenueShareRegion, Konkan]
-
A.
revenueDivision
chosen
Indicates how total revenue is allocated or split among different parties or components.
-
B.
distributorTerritory
Indicates the geographic area or market in which a distributor is authorized or responsible to sell or distribute products or services.
-
C.
suppliedRegion
Indicates that one entity serves as the geographic or administrative region from which another entity receives its supply or resources.
-
D.
oilRevenueSharingRatio
Indicates the proportion in which oil-generated revenue is divided or shared between involved parties.
-
E.
sharedStadiumRegion
Indicates that two or more entities use stadiums located within the same geographic region.
- 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_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.