Triple
T26289734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharashtra |
E661233
|
entity |
| Predicate | borderDisputeTimePeriod |
P28865
|
FINISHED |
| Object | since 1950s |
—
|
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: since 1950s | Statement: [Maharashtra, borderDisputeTimePeriod, since 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDisputeTimePeriod Context triple: [Maharashtra, borderDisputeTimePeriod, since 1950s]
-
A.
borderDisputeResolvedBy
Indicates that a previously contested border between entities has been settled or resolved through the specified agent, process, or agreement.
-
B.
disputeEndTime
Indicates the point in time at which a dispute is considered resolved or officially concluded.
-
C.
disputeDuration
Indicates the length of time over which a dispute persists or remains unresolved between parties.
-
D.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
E.
conflictPeriod
chosen
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 26, 2026, 10:07 p.m.