Triple
T14282839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bogra Formula |
E354092
|
entity |
| Predicate | soughtToBalance |
P9277
|
FINISHED |
| Object | representation of East Pakistan |
—
|
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: representation of East Pakistan | Statement: [Bogra Formula, soughtToBalance, representation of East Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soughtToBalance Context triple: [Bogra Formula, soughtToBalance, representation of East Pakistan]
-
A.
aimsToBalance
chosen
Indicates an intention or effort by one entity to bring multiple elements, forces, or conditions into a state of equilibrium.
-
B.
soughtTo
Indicates that one entity attempted or intended to obtain, achieve, or bring about another entity or outcome.
-
C.
soughtToMaintain
Indicates an entity’s deliberate effort or intention to keep another entity or condition in its existing state over time.
-
D.
balancesInterest
Indicates that an entity manages or adjusts multiple interests or priorities so that none is disproportionately favored over the others.
-
E.
forceBalance
Indicates that the net forces acting on an entity or system are in equilibrium, resulting in no overall acceleration.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697d9fd08190b0cd7a6a6737ba03 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.