Triple
T16090739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Provisional Government of Bangladesh |
E390352
|
entity |
| Predicate | effectiveStart |
P83226
|
FINISHED |
| Object | 1971-04-17 |
—
|
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: 1971-04-17 | Statement: [Provisional Government of Bangladesh, effectiveStart, 1971-04-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveStart Context triple: [Provisional Government of Bangladesh, effectiveStart, 1971-04-17]
-
A.
effectivePeriodStart
chosen
Indicates the date and time when a specified condition, status, or agreement becomes valid or goes into effect.
-
B.
effectiveFor
Indicates that one entity successfully produces the intended effect, benefit, or desired outcome for another entity or condition.
-
C.
lessEffectiveAt
Indicates that one entity has a reduced ability or lower level of success in performing, influencing, or achieving a particular action or outcome compared to another.
-
D.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
E.
rulesEffectiveUpon
Indicates that a set of rules becomes valid, applicable, or enforceable starting from a specified time, event, or condition.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.