Triple
T32426028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bisket Jatra |
E828578
|
entity |
| Predicate | tugOfWarBetween |
P100279
|
FINISHED |
| Object | upper town residents |
—
|
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: upper town residents | Statement: [Bisket Jatra, tugOfWarBetween, upper town residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tugOfWarBetween Context triple: [Bisket Jatra, tugOfWarBetween, upper town residents]
-
A.
engagesInCyclicalStruggleWith
Indicates a relationship in which two entities are locked in a recurring, back-and-forth conflict or opposition that repeats over time.
-
B.
tieForFirstPlace
Indicates that two or more competitors share the highest rank or score, resulting in no single clear winner.
-
C.
wasContestedBetween
Indicates that an event, position, or resource was the subject of competition or dispute involving two or more opposing parties.
-
D.
involvesRivalryBetween
chosen
Indicates a relationship in which two or more entities are engaged in rivalry or competitive opposition with one another.
-
E.
takesPlaceBetween
Indicates that an event or interaction occurs within the temporal or spatial interval defined by two reference points.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c287740c8190a91da975e50564dc |
completed | May 3, 2026, 3:35 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:54 a.m.